Hey,

Now this is a total "gut" opinion so take it for what's it worth. Sergey, please chime in.

When writing test code for VFP at MS, we used to run into this and similar errors a lot. It took us a while to figure out but the practical upshot was that VFP just doesn't grab and release record and file locks quickly and if one process or even the same process tries to do something too quickly an error occurs. The latency for VFP file IO is more geared towards the older and slower world and it's really easy for VFP to attempt to grab data or a file before the last process has let go. So we used to put WAITs of a few seconds between file ops in our code to account for it.

Frankly, I'm not sure what would be done about this. Perhaps Michel Fournier, the boss of the UT, might have some insight since the UT was (is?) VFP based with a high transaction volume.

>We are maintaining an Web application developed in ASP and backend being Visual FoxPro 8. We create/build Web DLLs in Visual FoxPro 9 SP1 and they are used to act as a bridge to the web application and the backend tables.The Visual FoxPro DLLs are configured as COM+ components.
>
>We have error handler in our web application. Consistently, we receive error mails from, "Error 1104: Error reading file". The thing is it get solved immediately without any manual intervention.
>
>We could not able to figure out the cause of this error. Please guide us.
>
>Earlier the web dlls are built in VFP6 SP5. We received this error 1104 mails consistently. We had migrated web dlls from VFP6 SP5 to VFP9 SP1. Even then we had received this errors consistently.
>
>Please let me know that simply migrating from VFP6 SP5 to VFP9 SP1, the application will be running with VFP6 SP5 behaviour.
>
>Is there anything we have to perform for migrating VFP6 SP5 to VFP9 SP1 like
>1) Is there any specific compilation steps to be done?
>2) Is there any environmental settings changes to be done ?
>3) Is there any mandatory steps to be done?
>
>Thanks,
>Sukumaran