System Recource Exceeded using TransferText

[Guest]

The following is the statement causing the problem:

DoCmd.TransferText _
acImportFixed, _
rsFileName.Fields("strImExSpecification"), _
rsFileName.Fields("strTable"), _
rsFileName.Fields("strFile"), _
False

It was running fine and created two .txt file in a folder. The third hit on
this statement has error showing "System Recource Exceeded...".

Do you what is the cause of the problem and what is the resolution for it.

Thanks.

 

[Wolfgang Kais]

The following is the statement causing the problem:

DoCmd.TransferText _
acImportFixed, _
rsFileName.Fields("strImExSpecification"), _
rsFileName.Fields("strTable"), _
rsFileName.Fields("strFile"), _
False

It was running fine and created two .txt file in a folder. The third hit
on this statement has error showing "System Recource Exceeded...".

Do you what is the cause of the problem and what is the resolution
for it.

Maybe, the Textfile is too large? Or the specification os corrupted?

 

[Guest]

Thanks Wolfgang Kais.

I have new information on this problem.

The problem actually occurred on a database file.

Rather creating the .txt file using "TransferText" I tried to do the export
text manually.

When I export text using the default spec and option as delimited I was able
to transfer the text successfully. However if I export text using the defined
spec (which is using in production, in this case is fixed width) I ran into
"System Resource Exceeded" error.

I am still trying to figure this out. In the mean time, suggestion from
anyone is welcome and appreciated. Thanks.

 

[Guest]

I just want to add this.

The file is small just 751 records and the record length is 465 bytes.

 

[Guest]

Ok. After days of frustration, having the problem area narrow down, finally I
have the problem resolved.

This is a tough problem to solve. It is because of the error message from
Access is misleading and vague. May be Access don’t even know what the
problem was. Anyway, having this problem and solution posted may help someone
if they run into the same situation.

The problem occurred was not file or record size limitation. It was because
of the Export Text specification is corrupted. I have quite a few Export Text
specification defined but this particular one is corrupted. How it is
corrupted I still don’t know. All I know that this problem occurred after the
PC is migrated to a different domain.
There is no way you can tell the specification is corrupted even if you
check the Export Text Specification before exporting data from the database
to a text file. It is because the Export Text Specification displaying on the
screen is correct.
To have the Export Text Specification corrected you have to do the Export
Text manually (e.g. right click on the database file and choose Export)).
When you are in the Export Text Wizard, follow the directions in the dialog
boxes. Click Advanced to create or use an import/export specification.
Actually you need to delete the old Export Text Specs, add and then save the
new Export Text Specs back into the database. As soon this is done the new
specification is saved in the database then you can finish the Export.

If the “System Resource Exceeded†message not showing up and the text file
is created properly after Export then you can try TransferText in your
program. Hopefully this time TransferText will work for you.

Good luck.