Hi Kevin,

I didn't forget about your question. :)
I would rather add datetime "lock" field to the table. You would fill it with current datetime to lock record and clear after update is done. The only problem with this method that you would have to clear that field in case if application blows up so record wouldn't stay locked indefinetely.


>What do you think of this as a workaround?
>
>When a record is made available to edit by a user, create
>and maintain a low-level file on the network which is named
>the same as the primary key of the record.
>
>You could release the file when the record was saved
>
>If the file is not there, or is not locked, the record is available
>for editing.
>
>if the file is there, and locked, then another user has that record open.
>
>Your thoughts?