Navigating Records in Access 2000 via ADO

[logo]

Ok, here's a mind boggler!

I am using VB's adodc component to connect w/ Access 2000. My table is set up w/a primary key which is simply an auto-incrementing field. When I add a new record it appears to be appended to the end of the table. . . . BUT . . when I move back through the recordset that is not the case!

I currently have aprox. 200 records in this table. When I "add new", "update", and "move last," my new record does not appear. Infact, instead of showing up as the 201st record, it shows up as the 130th (or so) record. If I check its index in ACCESS it is indexed as record #201.

Any ideas? What am I missing here?

 

[sebpas]

Is there any sorting applied to your recordset? If so, when you insert a new record, it will also get sorted therefore appearing somewhere in the middle.
Tell me if this is the case and the code you used to create your recordset.

 

[logo]

I'll have to think about this!

My table (w/in Access) is only sorted via its primary key (an auto imcrement).

Withing my VB app. there is quite a bit of sorting that goes on depending on what you are doing. Most of the sorting takes place w/in combo boxes which are not tied directly to the ADODC controls. (But now I want to go back and double check all of these) When you choose to add a new record I instruct the adodc component to "movelast", then "addnew," . . . perhaps one of the controls which is bound to the ADODC is actually affecting the placement of the curser in Access--its hard to believe, but it is an avenue which I have not explored. . .you've got me wondering...I will definitely continue analyzing my table...and components . . . .this, ofcourse, is no small task.