Dear Thomas,

I use this very same approach to restrict the number of connected users.
I have 2 notices for you:
- This lock release problem occurs only in case of error. Even if the rlock remains in effect, the same user (from the same machine) can rlock again the previously rlocked record. (So I always rlock all a availabe records and release them except 1. (It works well in case of restart after error.))
- The rlocked record remains locked as long as
--1. Server "thinks" that the workstation is still alive, - protocol dependent
--2. timeout isnot elapsed. (When inactive user is logged out rlock releases)

I had no problem on NT4 and Novell 3.12 and 4.0 The timeouts that I have faced varied till 15 minutes

bb

>I am working on a user license routine that adds a record to a table and locks the record when they are logged into the system. I can then use this data to pull a list of users or count how many people are using the software and not let them exceed their number of purchased licenses. I can also see who is in the system so if we need to make changes and someone is logged in we can go straight to that computer and get them out.
>
>This software is ran in a large manufacturing environment so it is crucial to have the ability to know who is in and how many users are in.
>
>We are having problems with the RLOCK() not getting released on some NT servers. Some sites the code runs without a hitch and some the NT server will not release the locks on the record.
>
>Has anyone ran across this problem? Is there a way around it?
>
>Thanks in advance.
>
>Tommy Martin