Hi Gregorio,

Thanks for the info. We tried deleting the foxuser table for the client, but the problem persisted. The problem ended up having something to do with the file they were attempting to import. I asked them to import files for other days - and there were no problems. But for this particular day, they receieved Error 18 - and I did not (and we are running the same exe).

The solution to this problem was for me to import the "problem" file on my P.C. and e-mail them the dbf and cdx files for the target table. I still haven't determined the cause of the problem. The type of file they were attempting to import is a standard file that comes off one of our mainframes.

Hopefully, I'll be able to figure out what caused the problem - but in three years that this app has been used - this is the first reported incidence of Error 18 occuring.

Al



>Allan:
>
>This problem of the foxuser file is not documented but as a programmer for long time in visual foxpro and foxpro for dos, this kind of problem that Tracy told you is real. The file by some reason start growing and growing and get sometime size so big that compromise the memory available and can cause you the problem error 18.