Has anyone experienced (and preferably, solved) problems with

Autonumber fields after a DB conversion from Access 2 to 2000?



We've experienced the problem on *some* of our PCs only, so we

suspect that it may be caused by something like a different

version of a DLL.



The most obvious symptom is that for some users, after

converting the database, autonumber key fields for tables

with records can generate unexpected next values. For example,

a couple of tables with two records show values of 1 and 2 for

the existing records, but new records added to these tables

get autonumber field values of  -6463994 (instead of 3) and

 -6463993 (instead of 4).  I have checked that the FieldSize

property for these fields is Long Integer, and that the

NewValues Property is set to Increment.



Other reported symptoms are:



  * duplicated values of autonumbered fields,

  * reports from Access that records could not be found when

    SQL UPDATE queries were attempted in Access 2000, even though

    SELECT queries with the same WHERE clause worked OK.



I've searched the MSDN Knowledge base on the web and CDs, with

keywords chosen from [Access, Conversion, Autonumber, 2000, 2],

without finding anything clearly relevant.



Thanks in advance for any information,



Peter Biddlecombe