>But this might be what I call process locking... you only wan't to allow one user at a time to carry out a certain task. This can be done quite simply with an extra field in the user table called "process". A form, or any process which can only be processed by one user at a time can be given a unique name/identifier programmatically and stored in that users "process" field. Before this is allowed you check the user file to make sure that no other user is undertaking that same process. The advantage is that you can advise the user "You can't do this just now because John Brown is doing it" - something that's much more difficult with record locks. Just clear the field when finished.

>If you don't have a user table create a ddummy one and assign psuedo userids at login to your system.

Denise,

To add a note to David's explanation... Its also simple using his method to devise code that will advise the prospective user when the record is once again free. That way the prospective user does not have to check back repeatedly to find out if he/she may commence editing or whatever he/she wants the record for.

regards,