Pleased to crack you up...
But I essentially agree with you. My problems were highlighted precisely because I am migrating things from Excel being used as a database to a database. That migration has taken massively longer than it should because the data has been altered by passage
through multiple versions of Excel. Even though the original (perhaps even Excel 98) had the fields marked as text over the years and versions the user-applied format has been disrespected because Excel knows best.
The root causes are clearly that: one Excel is easily available; two it does come with clear warnings that it is not a safe place to put data; three Access or another database is / was not typically available or familiar to the administrators who start a
process.
I still find it "amusing" that if I enter 12-2-9016 Excel is confident I mean a date in 7000 years from now, whereas if I tell it that 12-2-1889 is a date that is utterly incomprehensible to it. Time started on 1st Jan 1900.
So maybe I find myself wanting Excel always to store what was entered, exactly as it was entered, and to give me options for how it represents it. So that 12-2-9016 can be stored as precisely that text but I can ask Excel to render it as 12th Feb 9016 or
to treat it as the number 2599109 in a calculation.
In the meantime I have migrated to an XML database and have no reliance on anything to do with Microsoft for the particular business need.