Rick Winford <[log in to unmask]> wrote:

>I'm working with a customer developing a fairly large-scale application
>using multiple Turbo databases (like about 15).  We're trying to establish
>a mechanism to enforce locking rules, since we are locking multiple
>data bases over the life of a transaction.  I want to have a "standard"
>which dictates the order every program uses to lock the multiple databases,
>and then have some way to enforce programs to do that.  We are localizing
>all DBLOCK calls into one copylib, so enforcement should be rather easy,
>if I can just figure out some nifty way to do it.

Several years ago I retrofitted an application with Dynamic Rollback and had
to do the same kind of thing.  I too isolated all of the DBLOCK calls in a
copylib then replaced the formerly "inline" DBLOCK calls with a macro which
would add lock descriptors for predicate locks for when the DBLOCK was
actually called.  There's some other stuff I that I found necessary to
effectively manage the transactions as well, but I won't go into detail
here.

If you want more details, send an e-mail directly.

Regards.

 -- Evan