[AccessD] Curious Import Problem

[John Colby]

If I had to guess I would say there was bad data in the rows. Missing 
fields, bad data for the column type etc.


On 7/13/2016 10:21 AM, Heenan, Lambert wrote:
> X-Posted to Access-L and Access-D
>
> I'm posting this just as an FYI. Not seeking an explanation (though if anyone has one please post it).
>
> Here is the story.
>
> I'm loading a large (130,000+ row) CSV file into a staging table, where some pre-processing is done on the data, and then the whole lot is copied to the final table.
>
> Recently the users notice some rows of data were missing.  I confirmed that they were indeed present in the original source table, but on investigating I found that they simply never made it into the staging table.
>
> Importing was done by using
>
> DoCmd.TransferText acImportDelim, "Name Of Import Spec", "Name of Destination Table", "Full path to CSV file", True
>
> No error were thrown, and no Import Error tables were generated to explain the missing data.
>
> After pondering this for a while I changed the initial import process. Instead of using DoCmd.TransferText I simply *linked* to the CVS text file, using the same import spec as I used for DoCmd.TransferText. Then I created a straightforward Append query based on the linked text file to append all the data to the staging table.  That did the trick. All rows were loaded.
>
> Very odd.
>
> Lambert

-- 
John W. Colby