>>>Then with buffering off, maybe transactions would help. You cannot know without trying.
>>>
>>>Did you lower sys(3050) ? Did you try sys(1104) ?
>>
>>I tried the settings you posted and got an error right away. However, I'm not sure I tried it with the fresh set of data. I removed this code since then.
>>
>>If you want, I'll e-mail you LoadNewTrans program. You would not be able to run it, but you can examine it and may be something will jump into you that I overlook.
>>
>>If you're busy and don't want me to e-mail the code, that's fine too.
>
>Nadya,
>
>I'd be surpirsed if there were anything wrong with the program
>
>It's a vfp BUG. And you have to find a way around it
>
>Maybe it's a setting you have to change, maybe things have to be done in another way, maybe a combination of both
>
>You won't know if you do not try

The main problem is that we're just shooting in the dark. As for buffering/transaction configuration we can not make change because of the business logic. The changes should be either all committed or all rejected.

TABLEVALIDATE = 7 was suggested by MS while back when there was another problem with this process.

The Help on the error says: record your last actions and call MS. I don't know the phone to call and what exactly should I tell. The error is definitely reproducible in about each third attempt. I haven't yet tried all suggestions from this thread. It's actually not even my code to begin with, though I took it and modified a lot.

Also in production we're not going to run this program multiple times and we're not going to reload old batches, so the problem may not appear at all. It does, however, repeat in my tests with old already loaded batches.