MSACCESS.exe Error

[Bobbyd]

I have been building a utility that involves importing data, manipulating it and exporting it as text files. The utility is almost finished however I have recently started getting an error message for no apparent reason.

The error message reads as follows:

MSACCESS.exe has generated errors and will be closed by Windows. You will need to restart the program.
An error log is being created.

I have found that the error is generated at one particular line of code:

DoCmd.TransferText acExportFixed, VarTabName(0, IntCounter) & " Export Specification", VarTabName(0, IntCounter), StrFileDes & "\" & VarTabName(0, IntCounter) & ".txt", False, ""

This is part of a loop where IntCounter is incremented each time. The loop works fine until it attempts to export a specific table at which point it displays the above error and closes Access completely.

The table that it is trying to export is particuarly large, about 265000 records with 10 fields one of which is a memo field.

The problem has only just started and when I began investigating it disapeared but has returned. I have tried running the utility on two different pc's but the fault remains.

I have searched the net for possible answers, some suggest upgrading to Access 97 SR-2 others suggest upgrading to the latest jet engine, neither of these solutions solved my problem.

I am using MS Access 97 on a Win2k PC.

Any suggestions would be greatly received.

Many thanks
Rob

 

[Dugantrain]

You'll also probably get suggestions to import all of your objects into a new database as well as using the Jet Compact Utility which you can download for free, but neither of these tricks ever seems to work for me. What has worked, however, is to copy all of the code from the offending Module, paste it into a text file, Delete the Module, and then repaste that code into a new Module.

 

[Pat Hartman]

It is possible that you have run into some internal limit that is causing Access to abend. Perhaps upgrading to a newer version will solve the problem or limiting the text extracted from the memo field.

 

[Bobbyd]

I THINK I have solved the problem.

I tried to manually export the table and it failed in the same way, I then tried exporting the table without using the pre saved Export Specification and it worked without any problems. I then re entered the values into the Export Spec, saved it overwriting the previous one and it worked without any problems.

I can only assume that the MSysIMEXColumns or MSysIMEXSpecs table became corrupted.

The bad news is that it is now happening to another table and overwriting the spec doesn't solve the problem. I am going to delete the spec and start with a new one.

Many thanks for your suggestions.
Rob