J
John
Hello All:
We have an internal application to track revenue receipts. This application
is in production from last 4 years (Developed on Access 2000 and upgraded
thru 2003 SP1 without any issues). In that application, we have following
block:
1. Begin transaction
2. Record insert to Master Table, which would create unique payment tracking
number
3. Record inserts to Child tables with payment tracking number as the key.
(Note: Relationship defined between Master and Child Tables)
4. Commit Transaction
Last week, we applied SP2 and now the above code is broke. Now, we are
getting error message during the Child record insertions that the master
record doesn't exist. Thru debugger I couldn't notice any obvious errors.
If we add Commit Txn & /Begin Txn between step 3 and 4 (thus making master
and child record insertion as two separate transactions), then the code
works without any errors (even though we don't want to do the same to avoid
hanging Master records)
This makes us to believe that the changes happened within the transaction is
somehow not visible to the same session after upgrading to SP2. Any
assistance you could provide to resolve this issue will be highly
appreciated.
Thank you,
John
We have an internal application to track revenue receipts. This application
is in production from last 4 years (Developed on Access 2000 and upgraded
thru 2003 SP1 without any issues). In that application, we have following
block:
1. Begin transaction
2. Record insert to Master Table, which would create unique payment tracking
number
3. Record inserts to Child tables with payment tracking number as the key.
(Note: Relationship defined between Master and Child Tables)
4. Commit Transaction
Last week, we applied SP2 and now the above code is broke. Now, we are
getting error message during the Child record insertions that the master
record doesn't exist. Thru debugger I couldn't notice any obvious errors.
If we add Commit Txn & /Begin Txn between step 3 and 4 (thus making master
and child record insertion as two separate transactions), then the code
works without any errors (even though we don't want to do the same to avoid
hanging Master records)
This makes us to believe that the changes happened within the transaction is
somehow not visible to the same session after upgrading to SP2. Any
assistance you could provide to resolve this issue will be highly
appreciated.
Thank you,
John