Lincoln,

Glad to hear that progress is being made!

This locked-up record/screen - was that in a test or in "normal" usage of the system?

The reason I ask is simple - VFP was doing just what you would want it to do, given the way you have specified things. *IF* the general usage of the system is *NOT* at all likely to see two or more users wanting the same record at the same exact time, then things should be OK as they are.
However, *IF* it will be common practise to have two users accessing the same record(s) at the exact same time, then things should be changed.

The "advantage" of the present operation is that user changes CANNOT collide (and if the current holding user is nearby it won't take long for someone to yell that CUSTxxx is tied up and please finish fast) and the disadvantage is that the wanting screen stays "locked" until that happens. Obviously, if this should not really occur in day-to-day-use (that 2 users want same record at same time), then it should not be a REAL problem.

Good luck,

Jim N

>You lost me on the data bound/unbound interface. I'm a novice and need a little more specics. Or at least where to find more specic info. Thanks.
>
>As to buffering, my form has pessimistic buffering set. I have multilocks set to on. I have exclusive set to off in the init method of my form.
>
>Thanks for your help.
>
>--lincoln