I am having an issue with importing Excel Data into my SQL 2005 Table.
My first issue was the inablity to import mixed data types. Upon
research I implemented to the following:

In SSIS added IMEX=1 to the datasource string
Modified Registry TypedGuessRows=0
Formated Column as Text

This resolved importing mixed data types however I noticed that some
values are now coming over as scientific notations. An example of this
is as follows:

Excel Spreadsheet value = 100110004
Imported into SQL As = 1.0011e+008

Has anyone else run into this issue? I was able to work around it by
retyping those values in the worksheet. I am lucky that I only had this
one instance but I fear in the future there will be more. The fact that
the driver takes the liberty to make conversions to your data without
alerting you is an uneasy feeling. Does anyone have any answers or
suggestions to this issue? I'm sure I can add a task to my package that
will do a check on the data and let me know Thanks in advance!!

Indeed, one of the "artificial intelligence" features of Excel. Before you
fill the Excel spreadsheet, select all cells and format them as Text, then it
should work.

If Excel interprets you number as "scientific", you cannot display it as a
"normal" number again using the Text formating. You can using "Number" with 0
decimals. But displaying that again as "Text" returns you to "scientific".
Isn't that just great.

Perhaps you can work around this by programmatically formating the column as
"Number" with 0 decimals?