>I have a VFP5 application that accesses a free (FoxPro 2.5) table that resides on a Windows NT 4.0 Server.
>
>On occasion, when a record is changed in the table from a form, and then the form is released, the record will remain locked until the user exits the application completely.
>
>I always thought that when the form (with a private datasession) was released, all associated tables are closed and all locks removed. Is this right?
>
>-------------
>
>Also, are there any unusual "data cache-ing" issues associated with tables residing on NT Server, where data written back to the table may not be actually committed to the hard disk for immediate visibility to other users?
>
>
>Thanks for any ideas,
>Chris

If you're explicitly locking a record, are you explicitly releasing it when you're done with it?

As for NT Server, there is an Opportunistic Locking setting that is "on" by default, which needs to be "off" for some apps. I don't know if VFP or "VFP accessing free tables" is one of them.

http://support.microsoft.com/support/kb/articles/Q129/2/02.asp