ZZartin (7/26/2016)
Phil Parkin (7/26/2016)
ChrisM@Work (7/26/2016)
BrainDonor (7/26/2016)
Somewhere deep within the bowels of Microsoft there's a team of developers who believe that there's nothing at all wrong with the way SSIS ascertains the metadata for the columns within an Excel spreadsheet.One day I would like to meet these people, but only if I have full immunity from prosecution.
Very well put, Steve.
If you like I'll hold 'em down whilst you perform the surgery.
This is one team I'd like to be a part of.
If we could also get hold of the related Excel team who believe it's OK to open a text/CSV file and, without warning, alter the data it contains – "because Excel knows best" – I'd pay handsomely.
I would really like to have a discussion with the
geniustool bag who thought scientific notation was the appropriate format for large strings of numbers :angry:I wonder how many hours are wasted each year forcing excel to open documents like that properly and explaining to less technical people that excel just mangled their data with no warning.
Hey, who needs leading zeros, and who needs a 16 digit number with the 16th digit anyway? Even with the CSV file has double quotes around the number.
I spend way too much time trying to convince people that sending data as an Excel spreadsheet is a bad idea.