Re: custom locking in master-detail form

[Quoted] Tough one,

The inserts are what really complicates things. There's no good way to lock an insert record that hasn't been

   created yet.

If you have design priviledges, I'd add a database table to store

   the master record's identifier, and the username for the session    modifying records.
The client app would check the table before doing anything. The client app would also have to store (commit) this info when they

   select to change detail records. Later, when they're done, they    would have to delete the record.
   Might be a nice idea to wipe out any of client's records when they    first log in, so there'll be a way to clean up if the client    dies in the middle of making changes.

Good luck, Rich

In article <7k93dv$vuj$1_at_nnrp1.deja.com>,   bdg_at_hotmail.com wrote:
> In a Developer/2000 master-detail form, how to you prevent users from
> concurrently inserting/deleting/updating detail records for the same
master
> record?
>
> I would like for the first user that displays a given master record
to have
> exclusive DML access to the corresponding detail records. Subsequent
users
> should be able to view both the master and detail records, but
perform no
> changes.
>
> The master record happens to be query-only in this case if it makes
the
> problem easier.
>
> Thanks,
> Brian Gastineau
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Thu Jun 17 1999 - 23:19:55 CEST