I am guessing you have a majority of columns that may appear to be numeric, but also some that are pure text.
ADO
effectively ignores the column type
when importing an Excel. Instead, it guesses the column types, as stated in this MSDN link:
A Caution about Mixed Data Types
As stated previously, ADO must guess at the data type for each column
in your Excel worksheet or range. (This is not affected by Excel cell
formatting settings.) A serious problem can arise if you have numeric
values mixed with text values in the same column. Both the Jet and the
ODBC Provider return the data of the majority type, but return NULL
(empty) values for the minority data type. If the two types are
equally mixed in the column, the provider chooses numeric over text.
One way to load all fields as strings is to use the IMEX extended property
in your connection string
like following:
Provider=Microsoft.ACE.OLEDB.12.0;Data Source=c:\myFolder\myExcel2007file.xlsx;
Extended Properties="Excel 12.0 Xml;HDR=YES;IMEX=1";
Setting IMEX to 1 makes ADO treat all columns as text, as stated in following ConnectionStrings page:
Use this one [IMEX=1] when you want to treat all data in the file as text,
overriding Excels column type "General" to guess what type of data is
in the column.
You can find more information about the IMEX property in this SO question.
Update: The field data type retrieved using this would be ftWideString
.