Originally, I thought your problem was that one user started transaction1
and another transaction2. Seeing that the discussion has changed into
nested transactions, I must say that I am back to wondering why you need
more than one transaction. If you had only one transaction, your post to
table BB would succeed. You say transaction 2 calls three to five
procedures, if you changed this so that these procedures were called by a
trigger on table BB, it would be similar to a having "nested transactions",
the post to table BB would fail and nothing get changed if one of the
procedures failed and you could let your user modify values before trying
posting again.

HTH,
Set

At 16:02 19.02.2003 +0200, you wrote:

>Hi all,
>
> I have a problem that must have solved very urgently.
>
>1 - I start a transaction1
>2 - Edit AA
>3 - Change a value at table AA
>4 - Post AA
>5 - Start transaction2
>5 - Change or insert a record to an another table (BB), one field at BB
>references a field at AA
>6 - The referenced value at BB is the row at AA that was edited and posted.
>7 - When I try to post the data at BB I get an
> "lock conflict on no wait transaction
> violation of FOREIGN KEY constrait "FK_XXX" on table "BB"."
> error.
>
>how can I achive to post the BB before committing transaction1??
>
>I hope I could explain the stuation??