>>
>>How is your record / file locking being handled? If the files are being locked, you'll never free a user until the one who has the file locked turns loose of the file. Recommendation, use record locking. Big big huge, can't emphasize enough, when you lock a record (or file for that matter) turn loose of it as soon as at all possible. In a multi user environment, this is critical to performance.
>>
>>One methodology that we use here is to use Views for the visibility of data. The views exist on the client side. A client DBC is created for the app on the user's local drive, and the views spin up from there. The only time the databases are locked is the instant during which the Fox engine writes updates made to their local view back to the original data. ** Note ** Any time you do an update, immediately issue a requery on the view to get the updates made by other users as well.
>>
>>This is only one way, but it does alleviate the locking problem.
>>
>
>In this app, I am using the Txtbtns class from VFP5 to handle the adding, editing, and saving of records. I see the LOCK() command in the update code of the class, but I am not exactly sure what the whole scheme is (table lock, record lock, retries, etc.) I just don't know how it does what it does, but I know that I sometimes get this problem when 2 or more people are using the software at the same time.
>
>Thanks for helping with this. What should I examine so you could help me some more?

******************************************************************************

Look into your buffering schema and the LOCK() method. To see what it is trying to do. VFox will handle the record locking on its own if you let it. It is preferable to let the engine handle it rather than trying to force it.

Regards,