Hi Peter,
Nothing seems untoward - although you haven't mentioned how big your mdb
file is. If it's more than a few hundred megabytes I suspect that the
process might be temporarily taking it past the 2GB limit.
Other things I'd try:
1) Scrutinise the text file using Perl scripts or ports of the Gnu
textutils to make sure there aren't any nasties or inconsistencies (e.g.
a line the wrong length). I suspect that null bytes in textfiles can
sometimes cause problems.
2) Cut out the Text Linking Wizard. Instead, create a SCHEMA.INI file
with the field specifications and use ODBC to connect (see e.g.
http://www.able-consulting.com/MDAC/ADO/Connection/ODBC_DSNLess.htm#ODBCDriverForText)
On Thu, 5 Aug 2004 18:57:02 -0700, "Peter Whitaker" <Peter
ascii text file, 250 mb in size, 450,000 records fixed width; I
have win2k pro, office 2k small business, added access 2003 for this
project, 380mb ram, 900mb virtual memory, 650mHz p3. So far, I have
contacted Microsoft and they helped me change the maxlocksperfile to the
Jet 4.0 to 2million. This did not work. I still get , "Link Text
Wizard out of memory" message about 30 minutes after import.open a large ascii text file. First, it take at least 40 minutes to
processes then gives me the message. I have 384 megs of ram and 1 gig
of hard drive left. What is going wrong??? Do I need more memory?