I would recommend a good way of cleaning up at the end of the day or when the first user of the day logs in though or else if they have crashes during the day (for whatever reason) it could leave those records still appearing as though they are still 'checked out' by another user and not available for editing from earlier in the day or even the previous day. You don't want to be called to cleanout the rlocks table everytime it needs it. Maybe a good administrative utility (form) that an advanced user can clear all old connections (locks).
Tracy
>Interesting reading. I guess using a seperate table isn't a bad idea. Not much more work and there's benefits. I'll give it a try.
>
>Thanks,
>
>Michelle
>
>>Hi Michelle,
>>
>>I proposed a method using a separate locks table here:
Re: Tracking record locks by WinNT user Thread #
566971 Message #
567036>>
>>More discussion on some of the issues involved at
RLOCK Thread #
576665 Message #
576665 (entire thread).
>>
>>
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"