Weird Access DB problem

[peck2000]

Here's a strange problem. I've built an Classic ASP application with an Access 2003 DB on the backend on my website to track my comic book collection. The site is running on a dedicated Win2003 server.

I'm very close to completing the project, bar a couple of tweaks ...

However, when I try to add a new comic (ie table row) via the ASP/HTML input form, I get an odd message.

Microsoft JET Database Engine error '80040e21'
 
The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again.
 
/publishing/comics/collecting/admin/addItem.asp, line 52
 

At first I thought it might be just bad programming on my part (and it may be, yet) but when I downloaded the DB from the server and tried to put in new items manually, the autonumber [Item ID] value had somehow set back to a much earlier number and was now duplicating ID numbers that were already in use by the DB.

I can temporarily cure the problem by creating a new DB and importing the data from the old DB, but when I put the new DB up on my server, I get the same problem again.

So now I'm thinking this is some kind of corruption problem. Has anyone ever heard of anything like this before?

Thanks in advance for any light you can shed on this,

Peck2000

[NeoPa]

I'm afraid not Peck :(
I can't think what would cause this type of behaviour I'm afraid. As you say it may be your ASP code, but it may also be connected with how ASP connects to the database. Only other ASP programmers would be able to help there though. You may want to post this question again there. I won't simply move this across as someone here in Access may yet be able to shed some light, but I wouldn't hold your breath.
Good luck with it anyway.