Sunday, November 30, 2008

ODBC Provider Bug?

ODBC Provider Bug?
James Hippolite
Friday 28-Nov-08 09:45

Has anybody heard of a bug in the ODBC provider for Excel where, if a column has 10 NULLS in a row, then the entire column comes in as NULL?

Paul Bibby
Friday 28-Nov-08 09:57

Don’t know if this is similar to your experience ?

http://www.stata.com/statalist/archive/2006-08/msg00457.html

Leigh Hunt
Friday 28-Nov-08 10:40

I ran in to I think the exact same issue a number of times years ago, importing mixed field types from Excel into Access, using the JET driver.

I think Paul's answer is probably the one your after, especially the links to http://www.dicks-blog.com/archives/2004/06/03/external-data-mixed-data-types/ and http://support.microsoft.com/default.aspx?scid=kb;en-us;257819.

However, I encountered mine about 8 years ago, using older versions of the software, so thought I'd post it here incase the above solutions don't fix it for you... (I notice one article states that the MaxScanRows argument doesn't work in a connection string - well it certainly works in the registry:

I changed the following entries in the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Text]
"MaxScanRows"=dword:0001869f
"ImportMixedTypes"="Text"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Text]
"MaxScanRows"=dword:0001869f
"ImportMixedTypes"="Text"

After this, all imports would work fine for me.

Cheers,
Leigh.

No comments:

Post a Comment