Jim,

>It has been close to three years since I last used VFP tables to store data other that metadata (which doesn't very foten get locked). I have been working almost exclusively with SQL Server and that does its own handling of locking. Essentially it has been close to three years since I last even thought about locking resources.

It begs the question, how do you lock resources now? Though the database has been changed, the requirement of semaphores does not change. How do you keep track of the number of concurrent users in SQL server. How you lock for example a invoice when someone is viewing it in order to prevent concurrent actions ?

Sure, there are a number of things that don't have to be handled via semaphores or mutexes, (for example when updating data, you can check if another user has not changed the data, and if it has, capture the generated error and handle it). However, when you're selling an application how do you limit the number of users working on the database in SQL server, while you still have to deal with potential crashed clients.

I'm wondering If you came up with the same solution as I did....

Walter,