[AccessD] Automating Excel imports

And I stand with the ADO recordset. You will not have to wonder
what Excel is doing to the data or what the linking or such is doing to it.


At 08:05 AM 6/23/2011, you wrote:
>Date: Wed, 22 Jun 2011 18:10:44 -0700
>From: "Darrell Burns" <dhb at flsi.com>
>To: "'Access Developers discussion and problem solving'"
>         <accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Automating Excel imports
>Message-ID: <010b01cc3142$60f0ad10$22d20730$@com>
>Content-Type: text/plain;       charset="us-ascii"
>
>Here's a clarification of the problem - it's not that the zipcodes are
>numeric, it's that SOME of them are alphanumeric.  For example, the first 30
>records contain numeric US zipcodes, then record 31 is a Canadian
>alphanumeric. Since TransferSpreadsheet determined the data type to be long
>integer from the first 20 rows, it pukes when it hits row 31.
>
>I tried linking instead of importing, but get the same error when I do an
>insert query. I also tried importing into a new table; the good news is that
>it didn't throw an error...the bad news is that the alphanumeric postcodes
>weren't imported at all. Kinda makes me wonder how much other data my import
>routines are missing!
>
>Looks like the only solution is the one you proposed, Mark.
>
>-Darrell

Robert L. Stewart
www.WeBeDb.com
www.DBGUIDesign.com
www.RLStewartPhotography.com