Are you doing a requery somewhere on the clone or original recordset. The 2
could be dissconected from each other. Judging from the MS doc's if you do
this then the clone looses it's parent. Not sure if this could be your
problem, but you may whant to look into it.
Also we find version 2.6 the most stable. If you are not tied directly to
2.7 in some way, try doing a simulation with version 2.6 or 2.8.
Depending on your db you may what to see if the table if being locked up by
another call though i am sure you have do this.
If your useing Storedprocs that have a cursor validate to make sure all are
being closed and deallocated.
Make sure all batch transactions have been commited befor adding to the
table, it could be a transaction locking up the table somewhere.
Plunk a doevents befor the addnew, maybe a stupid comment but amazing how
that simple command can get ya out of a pickle:)
Just a couple of maybe's, hope it helps....
"Rud Van horne" < XXXX@XXXXX.COM > a rit dans le
sp1, we have disconnected Recordsets alive all the life time in the memory,
and being updated all the times using Clone of the original Recordset, the
application is very demanding to add, delete, and update records in the
recordset. After a while and for no know pattern the application gives an
Unspecified Error 259 When adding a new record, we thought the edit mode is
not adEditNone, yet it was, the locktype is adlockoptimistic, and the state
is 1 meaning opened. The status was 8.
the application..that is the major issue to deployment...any help is needed
in this desperate situation.
nothing can be done to the recordset