I have a VB6/Access application that occasionally encounters a problem with wrong autonumber field seed.
Lets say there is a table MYTABLE with an autonumber field
You may also need to make sure that your database is set up to use ANSI 92 so that COUNTER is recognized as a legitimate data type.
In Access 2007 go to Access Options, Object Designers, SQL Server compatability syntax (ANSI 92) to set this.
You may be able to solve the problem with a compact/repair:
In Access 2010: Compact and Repair Database on the Database Tools ribbon.
In Access 2007: Office Button | Manage.
In earlier versions: Tools | Database Utilities.
Please reference the following article, it contains a method you may add to your access project to execute to reset seeding. It has been a saver for me several occasions in the past:
http://allenbrowne.com/ser-40.html
In addition to this it gives explanation and insight into causes and potential resolution for such problems.