Ah.

Don't know how much it helps but I do know that some VFP file functions use very old Windows routines that can require 2 or more seconds to complete. We had all sorts of timning issues with some of our test scripts because of this - false failures because the file wasn't released by the previous function.

As to a standing lock ... haven't seen it, sorry. Maybe that's something outside of VFP because I would have seen it in our testing due to the nature of our test harness.

>>Define "unlock"? Can you give a use case or scenario of what is happening?
>>
>
>I had cases where the network OS does not release a lock on a file. For example, my VFP app will open a file with fopen() and even after the application will be closed no one else can open this file. This is what I mean by "unlock" the file.