I was under the impression that when you pull data up into a window that the row is locked thru the window process. Is this true or not?

I'm working on a problem that may be a locking problem. In doing some reading, I came accross the TCL commnad of LOCKS (AREV 3.12 Reference manual page 243) which displays a report as to which tables and rows are currently locked. Since I was the only one in our development system there was nothing to see. Then I pulled up a data row by using a window and then checked the LOCKS report from TCL and it was still blank. I don't see how the TCL level would be a factor in displaying the locked rows and tables or not. So with what I've seen so far, it would indicate that a row in a window is not locked. Is this true or not?

Thinking that it may be my local network giving me a false reading, I connected to one of our remote locations and did the same thing with the same results. The remote location's network is setup a bit differently (I was hoping that in itself may help). Our local network is a Novell 4.x with our AREV application is running on an NT server and I'm using a Win95 workstation. The remote network I connected to is a Novell 3.X and the application is on the Novell network. Both applications I tested this on are duplicates of one of each other running under the AREV 3.12 OS.

Can anyone point me in the right direction?

Thank you for your time,

Michael Slack

This is a slightly confusing command. It is used only to display locks in transaction processing for commit and rollback.

Locking IS done automatically by screens - try calling up the same row from 2 machines - if you get a message on the second, locking is working.

For checking who has locks check out Steve Smith's excellent[/b] utilities page at State of the Art Sprezzatura Ltd World Leaders in all things RevSoft </QUOTE> View this thread on the forum...