A user got out of the record which had Exclusive lock. No system crash or no unusual exit. Still NLM_STATS keeps showing Record Locked by that user. What's causing this? User accesses database over WAN.

Also, does record gets released right away once Lock is released or is there any fixed time set up? Using AREV 2.12 with NLM

Thanks.

Hello.

Record locking is actually set by a token stored in the NLM/ Server. That token's value is a combination of the key value AND the DOS Name of the table that contains that record.

In my experience this has happened when you copy directories from outside of ARev into another directory, and, open both directories at one time. Thus, there are duplicate DOS Named files open at one time.

So, when you examine the situation from the ARev point of view, the locks are for different files, but, the locked token is identical.

Hope this help.

Dave

Thanks so much Dave. This is what happened. I had a user looking at a record with key=123456789 on EMPLOYEE table on volume ABC and then same user started another copy of AREV and pulled up the record which has same key and same table name but is on volume XYZ. She released the lock on the record on volume ABC and then released the lock on record on XYZ as well. But somehow it kept record locked on volume ABC till she got out of AREV. Is this something that would have translated into the NLM/TOKEN scenario that you are mentioning? If yes, then any way around it?

Thanks. All help greatly appreciated.

Thanks so much Dave. This is what happened. I had a user looking at a record with key=123456789 on EMPLOYEE table on volume ABC and then same user started another copy of AREV and locked the record which has same key and same table name but is on volume XYZ. She released lock on record on ABC and then she also released lock on record on XYZ. However it kept showing record was locked on ABC till she logged out of AREV. Is this something which would have translated into NLM same token scenario you are mentioning? If yes is there any way around?

Thanks. All help greatly appreciated.

Wow,

this means having "MODEL OFFICE" … the copy of real application for testing purposes on the same server is not good scenario as it locks records in real application.

Does it depend on 8.3 name only, or on the whole path (except disk:)?

Now, I made a simple test … the difference in the directory structure is sufficient. The records are not locked accross the applications in that case.

…. means problems can appear only with the same directory structure on diferent volumes on the same server … it doesn't cause probems to me;)

Naturally such copies for testing are made with full respect being paid to the article here and other licensing documents :)?

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

I hope yes, we use the same AREV.EXE (the same account), we only attach different volumes (different versions of the developping application). ;)

Yes - we cheat - we execute the SAME .EXE but have different working directories. That way we control the license count!

support@sprezzatura.com

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

View this thread on the forum...