There are two things you want to make sure of when you use RLOCK() the way you are:
- You don't use private datasessions.
- You don't open the main table EXCLUSIVE anywhere.
I think your problem may be with number 2.
>I have an application that allows users to retrieve records and edit them. They can also create new records and save them. There are a bunch of files involved but the main one contains a header record with a unique deal code. When the user retrieves a deal, I issue an Rlock() on the main file to prevent another user from accessing that deal. When they save a new deal, I issue a Rlock() on the deal record again. Before any Rlock(), I have "Unlock in Deal" because users will retrieve, make changes, save constantly. All I want is whatever deal they are working on to be locked.
>
>This works fine here, but we only test with one or two people. They have 12 people and they are getting messages saying the record cannot be locked. They insist that no two people are working on the same deal.
>
>Do different networks come into play here? Is it possible for a network to not allow VFP to lock/unlock consistently. If networks can change the way VFP handles locks, are there things the administrator can do to make it work correctly?
>
>Please help. Thank you.
