OK I kind of figured out what is happening and maybe you can explain why.
There are 3 users of this database at 3 separate locations. The main user does all of the data entry and changes and the other 2 use the data for reference. I have it set up that once a day the main guy uploads the most current data to a web server as a file. With the click of a button the other users can download that file and it will update their table using TransferDatabase and an append query. This all works fine for them because they do not add or edit anything.
I was able to reset the index with an append query, however, as soon as I downloaded that file from the server and it updated my data with an append query, the index got reset and I was getting duplicate primary key errors when I tried to add a record using the form.
Looking at the table after the download and update, the highest primary key number was 148384. However when I try to add a record, it wants to give it the number 148156 which already exists. That's where the problem lies.
So if the highest key # in the table is 148384, why is the autonumber not set to start at 148385 after the append? There are gaps in the primary key where records get deleted at times.