Reminds me of this classic
https://www.theverge.com/2020/8/6/21355674/human-genes-rename-microsoft-excel-misreading-dates
where scientists had to rename a gene because Excel kept mangling it into a date rather than string 😆
Reminds me of this classic
https://www.theverge.com/2020/8/6/21355674/human-genes-rename-microsoft-excel-misreading-dates
where scientists had to rename a gene because Excel kept mangling it into a date rather than string 😆
@steevmi1 @gumnos @mhoye I can reliably make Excel eval text in CSVs as expressions just by loading the CSV. CSV files are data not code unless you're working in Excel. I'm not sure if this is legacy Lotus-123 behavior but I expect CSV values surrounded by quotes to be treated as text strings and absolutely not as expressions to be evaluated.
Excel is an attractive hazard and not fit for purpose.
Hah, just hit this working a case for $DAYJOB yesterday, in which the exported-from-Excel CSV file had values like
="long string of digits"
to prevent long numbers (IMEI/SIM numbers) from getting converted to floating-point. Which is good, but mean that my CSV-handling importer had to strip off the wrapper that had been causing the value-extraction to give the wrong data. :sigh:
Unfortunately for a generation of scientists in institutions largely captured by the managerial class, Excel was the only tool immediately to hand that did not require a round trip through a procurement process with a constrained budget in one hand and a publication deadline in the other.