> I guess I am used to the MIDAS way, where you need a transaction for every
> Query/Table. Also, I like to have more control over what is happening, and
> that is why I have used two transactions. Is there a downside to doing this?
> I have always been told multiple transactions keep a tighter control over
> what is going on, by separating your actions.

This will only work if the transactions are handling
separate records - see below.

> Anyway, bottomline, I need to know how to cancel and delete items in the
> DETAIL, without compromising my ability to roll everything back if the user
> decides to cancel the MASTER.

I have a similar problem. I use the transaction for the
outer wrapper, i.e. all updates, so that rolling back the
MASTER clears everything. The problem is that you can't
'nest' transactions, so each DETAIL item has to be deleted
rather than rolling back a second transaction. In my case,
it is usually the case that a problem with a detail means
the whole order was to be cancelled anyway, until stock is
available to complete the whole order, but each detail item
can be changed to select a different batch code, or cancel
it. It just requires care when setting up your 'work flow'.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services