Importing Large Text Files

[lewis33]

Problem: I have a large text file that is about 87,888 KB and is about 200,000 records. It has about 34 fields of mostly text but has some number fields. I would think initially that it would not be too large to import into a table. However, Access generates error message "msaccess.exe has generated errors and will be closed by windows"- sometimes I'll get about 3,000 records to import and then it will shut down.

Any ideas on why this occurs with this file- I guess it's a memory issue but thought this would be a workable flat file.

Thanks yet again. Confused in Cleveland.

 

[RickSpr]

If I'm not mistaken, that message occurs on WinNT/2000/(XP?) systems when the application suffers a General Protection Fault, Invalid Page Fault or the like (errors that cause an uncontrolled abort by the OS).

It seems clear you've hit a bug in Access. The first thing I'd try is applying the latest maintenance to Access/Office.

Rick Sprague
Want the best answers? See faq181-2886
To write a program from scratch, first create the universe. - Paraphrased from Albert Einstein

 

[MichaelRed]

To add to. It is almost certainly not the actual size of the data being "imported". There are several retrievable (on these fora) which comfortably 'grab' 50+ MByte text files into 'MEMORY', easily including the 35+/- fields and howevermany records. I have generated processes which 'grab' (CSV) files of this nature, parsed them to individual field values and appended to a table.

That's the GOOD news. Now -the not so good.

Without knowing A LOT more than I really want to about the details of YOUR process, it is not possibe to state that YOUR approach will / will not work w/o error. Some details are -perhaps- critical, such as the source format, the 'connection' (and disconnection) process, wheather the source-destination mapping is "acceptable", ... etc.

Simply to state that you tried (whatever) and it am broke, certainly provides a multitude of possabilities, but few clues re the 'brokenedness'.





MichaelRed
m.red@att.net

Searching for employment in all the wrong places

 

[lewis33]

Gentlemen,
Thanks very much for the feedback- that gives me a good base to understand the problem. It's a basic import done manually throught the import wizard so I think I will try to check the microsoft site to see if they have a patch. Thanks again guys.

 

[lewis33]

Just imported it and it went fine. I'm thinking it is a file compression problem or some type of error is made when it is translated from a DB2 file into a text file. Thanks guys