Access97 ADO SQL7 transactions - undefined recordset after COMMIT
I have found that the connection that the recordset is opened on, must
be different than the connection that is being committed.
Quote:
> I have to transform an Access97 application using DAO-SQL7 to ADO-
SQL7.
> There is one behavior/bug/effect on using transactions.
> There is a recordset (Select ... inner Join ... - we can call "T1")
of up to
> 200 entries. For each entry there is to modify a record in another
table
> ("T2") and add a record in Table "T3". These 3 steps are coded in one
> transaction (NOT all 200 entries together in one big transaction). In
> DAO-MDB (and DAO-SQL7) this worked fine.
> But now (ADO) after the CommitTrans of the first entry all recordsets
opened
> over the connection are undefined. If I do a moveNext I get error
message
> <Schwerer Fehler>~?~<Critical Error>. Thats all!
> I have to do a requery, but after that the cursor is back on the first
> entry. => repositioning => bad performance ....
> Any Idea ????
Sent via Deja.com http://www.deja.com/
Before you buy.
