wiltonrossi
Programmer
Hello guys,
Yesterday I had a hell of a day due to a mysterious problem. There is a table in my site which is used to monitor access and for the generation of reports. Whenever the users visit certain pages a new record is generated inserting the user login (if he is logged), the page visited and the time it was visited.
It was working fine for two years until yesterday when I got the following error message:
----
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[TCX][MyODBC]Duplicate entry '278655' for key 1
/area_rest/MonitoraAcesso/default.asp, line 29
----
This file is reached via an include. The line is the one which inserts new data into the table and the number is, of course, the record, which goes into an auto-increment field. Needless to say that I never try to insert data into that field since it is not necessary.
So I tried to find what was going on and found out that the last record in the table is number 278654. In my despair, I thought that maybe the column had reached its limit. It was a 10 character int and so I turned it into a 14 character int.
It worked for a while and it started to accept new records, but, for my greatest surprise, I got the same error message again an hour or two later (with a different number, of course).
Anyone can tell me what is wrong?
Regards,
Wilton Rossi
Yesterday I had a hell of a day due to a mysterious problem. There is a table in my site which is used to monitor access and for the generation of reports. Whenever the users visit certain pages a new record is generated inserting the user login (if he is logged), the page visited and the time it was visited.
It was working fine for two years until yesterday when I got the following error message:
----
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[TCX][MyODBC]Duplicate entry '278655' for key 1
/area_rest/MonitoraAcesso/default.asp, line 29
----
This file is reached via an include. The line is the one which inserts new data into the table and the number is, of course, the record, which goes into an auto-increment field. Needless to say that I never try to insert data into that field since it is not necessary.
So I tried to find what was going on and found out that the last record in the table is number 278654. In my despair, I thought that maybe the column had reached its limit. It was a 10 character int and so I turned it into a 14 character int.
It worked for a while and it started to accept new records, but, for my greatest surprise, I got the same error message again an hour or two later (with a different number, of course).
Anyone can tell me what is wrong?
Regards,
Wilton Rossi