lbriner
2 days ago
Don't get me started on the automatic conversion of strings that it thinks are in scientific notation into numbers - which you can't switch off!
We have large data exports from systems that include things like unique location code. You accidentally happen to notice that a block of these look weird and it isn't just the display of them that has changed, the contents of the cell were changed by Excel automatically, without asking, and you cannot disable it.
Absolute BS after all these years. I hate that they won't fix these niggling issues that keep tripping people up over the years and just make excuses. Microsoft's usual response is: "We only work on things that affect a large number of customers". Yeah Microsoft, if you keep closing these bug reports, then each time someone reports it, you can just say that it only affects one person and close it again.
Or...you could show how amazing your company is by doing what most of us have to do: Fix it, add more debugging for the next time it happens if you can't recreate it, or have a properly tracked reason to say, "only a very few people have asked for this but changing it might break these other areas/bacwards compatability" or something.
vikingerik
2 days ago
Yes, it's that last reason. Backwards bug compatibility. There are zillions of recorded macros and VBA scripts and other workflows by non-technical users that inadvertently depend on these behaviors in subtle ways. It's like all Javascript's weird warts, you can't change these behaviors without breaking old stuff somehow. It's true that Microsoft could say that more directly, but of course they'd rather just avoid that argument.
tssva
2 days ago
Is there a reason you don't specify the data type when importing or if it is a frequently used data file format automate the import using VBA specifying the correct data type?
mark-r
2 days ago
If you open a CSV file without going through a specific import process, you don't even get the option to specify a data type. And once it's open it's too late to fix it, the original data is already gone.
tssva
a day ago
The specific import process isn't some sort of esoteric process. It is the data import wizard. Also as I said if you are regularly importing data from a file with the same format writing some VBA to do so is pretty quick and simple task.
Also your data isn't gone. It is still in the CSV file you imported it from. Re-import it.
mark-r
a day ago
I would wager more people open a CSV by double-clicking on it rather than using the import data wizard. And even if you use the wizard it takes extra work to specify the type of each column, which most people won't bother with.
Writing some VBA is a simple process if you're a programmer. I wonder how many genetic researchers fit that description?
P.S. when I said "too late to fix it", I meant by some process within Excel. Of course you can re-import the original file, but maybe you only notice the problem after you've done a lot of work with it?
tssva
a day ago
Expecting you to learn the basics about the tools you're using is not expecting too much. And if you are too lazy to spend a few seconds specifying data types then you get what you deserve.
fshr
a day ago
> Expecting you to learn the basics about the tools you're using is not expecting too much.
Do you/have you worked in a corporate environment? You seem to have an idealistic view about how end users are expected to use Excel.
tssva
a day ago
I worked in corporate environments for decades.
The original comment I responded to said they regularly imported large data sets and the in the case of the genetists they also are regularly importing data into Excel. In other words Excel is a regularly used and fundamental tool to their work. In this case I would expect someone to learn the basics of using it. Just as I would expect a developer to learn their editor, build system, version control system, etc.
XlA5vEKsMISoIln
a day ago
Excel chews up CSVs that it opens. I know this because an accountant checked each file our code produced using Excel before trying to import it into another program. We proofread our code before we realizing the problem was somewhere else. Shoulder-surfed the process, found the giant bug with a green X on it.
paledot
a day ago
It's no better at exporting to CSV. I wrote a CSV parser a few years ago that had one set of logic for Excel CSVs and a completely different set for everything else.
tssva
a day ago
Excel doesn't change CSV files when it imports them. If the imported file was being changed then the user was saving back to the same file they imported from.
XlA5vEKsMISoIln
a day ago
This information doesn't help anyone.
The fact is the person was double-clicking a file in a list to view its contents and Excel was trampling it. Nobody in their right mind will waste time to open Excel first, use import feature, re-navigate to the file they were already looking at, and go through the import dialog just to see what's inside.
tssva
17 hours ago
Trampling it to me implies that Excel was somehow modifying the contents of the file. Which it doesn't do by double clicking on the file and just viewing it. Do you mean that the data shown in Excel wasn't what was expected because of the auto data conversion?
XlA5vEKsMISoIln
11 hours ago
Believe me, I was blown away just the same. And it's not like the accountant clicked a save button of a on-close dialog, no. Opening a CSV file was enough.
RajT88
a day ago
> Don't get me started on the automatic conversion of strings that it thinks are in scientific notation into numbers - which you can't switch off!
Every week it bites me once or twice. Drives me bananas.
cynicalsecurity
2 days ago
Why still use MS Office when LibreOffice is freely available?
lotsoweiners
a day ago
Because that is what your work gives you and what all of your coworkers use.
wruza
2 days ago
Does it fix subj-related issues?