Hi doug,

>>But how can you limit the number of users when all data is on the SQL-server (thus the record lock strategy does not work here). How can this be as much bulletproof as we don't have any control over what a system administrator is doing. It should also handle crashed clients properly.

>Just because the application's data is in SQL Server doesn't mean that "system" data has to be. Why not use a VFP table for this type of semaphore information?

Well, I suppose it would be easy to trick the system by installing the same application twice in seperate directories, where a number of clients use the first dir and another number the second dir. Also, not knowing if this will be a requirement, but when working via a WAN you might want to have more than one VFP database connecting to the same server. This would make it impossible to check the number of concurrent users connecting to the database.

But of course,if this is not a requirement, I'll go for the VFP option.

Walter,