Have you tried using IMEX=1 (which seems to work equally in DAO and
ADO)? E.g.
SELECT * FROM
[Excel 8.0;HDR=Yes;IMEX=1;database=C:\folder\file.xls;].[sheet1$];
On Wed, 14 Mar 2007 21:07:24 -0400, "Alan B. Densky"
Hi John,
Thanks for the effort. I had the link to
www.disks-blog and went through
that information a while back. It didn't help because it just didn't
make
any difference when I edited the registry.
As far a Acess 2007 - I have no interest in spending the money,
upgrading,
or going through the learning curve.
My database is based on DAO, so the ADO isn't going to help me, and I
don't
want to go through the learning curve. I quit programming for money a
couple
of years ago, and now only program for my own business and a few old
customers. I don't have the time, energy, or desire to play the
Microsoft
"learn to do it our way, and we'll make make your learning investment
obsolete whenever we feel like it" game any longer. Especially since so
many
people are sending their work to Rent-A-Coder people for $5.00 a day.
Is there any other way around this issue? Maybe I'm just going to have
to
break down and do an import of a CSV file in a temp table?? It sounds
like
my only work-around that I don't have to go through a learning curve to
accomplish. Unless you know of some other way to trick Access to look at
all
of my linked columns for this particular table as Text columns.
Thanks again,
Alan
Hi Alan,
See
http://www.dicks-blog.com/archives/2004/06/03/external-data-mixed-data-types/
and
http://support.microsoft.com/?id=257819
and
http://msdn.microsoft.com/library/d...ns_programmatically_for_the_access_driver.asp
and
http://office.microsoft.com/en-us/access/hp010950951033.aspx
Also, consider upgrading to Access 2007, which offers more direct
control.
On Thu, 8 Mar 2007 20:27:31 -0500, "Alan B. Densky"
In Excel, any cell can contain any data, and the data may or may not
be
formatted in a particular way. In Access, by contrast, every field has
a
fixed data type and can only contain a value of that type ( double,
text, etc.). When Access imports from Excel to a new table, it guesses
the field types to use by examining the data in the first few rows of
the Excel table - and often gets it wrong. This can cause Access to
bomb
out during the import.
The "Fix" for this - according to another post, is to massage the data
in
the import. That is riciculous.
Does anyone have a way to fix this problem the right way?
Alan