Hi Jos,

Just an update. We've been going back and for with the client on this problem. Here are the the things we've done so far that worked for a while but generated the same problem after a few days:
1. Gave the log table a new name just in case the name we are using is a reserved word somewhere.
2. Changed all the memo fields to character fields 100 wide.
3. Had the user copy the app to a local PC and runn it there.

We've learned a few new things from the user though that they forgot to mention.
1. The user would reset the app/PC when the import was taking too long (over 10 min.). It should take just seconds since the text files are rarely over 10 Kb in size.
2. They have the database residing on an AS400 server.
3. The bloated table seems to have the data repeating over and over again (may be why it is taking so long) even though a browse does not show this.

I've already prepared a program that would cleanup the table but since this happens when the importing is happening, it won't solve the problem.

Thanks,
Arriyel

>Arriyel, given this new information its clearly not the program itself or the table. As Jim has already pointed out it must be something unique to that user who exhibits the problem. They are either tampering with the file, have something unusual in the files they are importing, virus issues(?), or perhaps even hardware problems. You will need to go through the "usual suspects"!
>
>
>>Hi Jos,
>>
>>Thing is this only happens at one installation (customer) only. We have over a dozen other customers that does not have this problem.
>>
>>We've tried deleting the files then recreating them as new but the problem just recurrs after a while. We never delete records in this file (well maybe after a year or so when they archive the database). Most of our other clients naver have this table over 1Mb in a year.
>>
>>We only use INSERT SQL command to add records to this table.
>>
>>Thanks,
>>Arriyel
>>