In a generic database class, I have a "SaveData" method which takes a
disconnected recordset as an argument. Then:

Set rs = new ADODB.Recordset
with rs
       .CursorLocation = adUseClient
       .CursorType = adOpenKeyset
       .LockType = adLockBatchOptimistic
end with

mConn.Open
set rs.activeconnection = mConn

with rs
        .Open disRS
        .UpdateBatch
End with

This works fine. The problem occurs when I try to retrieve the newly created
Autoincrement ID.

If the the index for the table does NOT include the Autoincrement field, then
this code works fine:
             rs.Resync
             SaveData = rs.Fields("ID").Value

If the index DOES include the ID field, Resync cause the error "row changed or
deleted at the data store". Plus, without doing the Resync, the ID field shows
0 in rs.

I'm using ADO 2.5 with the Jet 4.0 provider to access Access databases built
with VisData in VB6. It was my understanding that the 4.0 provider was supposed
to fix this inability to retrieve the new ID.

Anybody help me here?

Scott

Hi,

Retrieving the new record ID is not longer so simple under ADO then under
DAO. Try to work arround with an own created unique key.

Frank.

Well...yeah...I could use an API call to create GUIDs in the middle layer, but
that's not my point, and defeats the purpose of having a fully encapsulated
data access layer. The method returns the correct incremented ID when the table
index does not include an autoincremnt field, but fails when it does. I'm
trying to find out why, and how I can make it work in both situations.

Scott

If you use Access 2000 database then:

dim rs1 as New Recordset

SaveData = rs.Fields(0)

Resync - only for server cursor location method

Happy New Millenium!