T
Telesphore
Suddenly it is impossible to add a new record to the table tblStudents. The
Autonumber field StudentID primary key indicates 762 records.
It is impossible to add a new record in the StudentCode field which would be
number 08-1721. An error message follows: "The changes you requested to the
table were not suc-cessful because they would create duplicate values in the
index, primary key, or relation-ship, etc."
And more, the Autonumber field StudentID primary key indicates 386 instead
of 763!
Trying again had indicated 387, 388, etc. and it is still impossible to add
a new record.
On another working station, if one tries to enter a new record, StudentID
was 606! This Autonumber field gets all mixed up!
The back-end database IFTM_princip is located on a Windows Server 2003 and
the ta-bles on the front-end database IFTM are linked tables in each user.
The users work on individual workstations Windows XP.
The Msjet40.dll version is 4.0.9511.0
We installed the SP3, but the problem remains still the same.
Any ideas?
Thank you
P.S. However I realized that Access has accepted an autonumber whose record
had been removed. Would it be that Access does not like that record may be
removed in a table? There had been 42 records removed all together. I
checked those missing numbers. So the users will try to use them.
Autonumber field StudentID primary key indicates 762 records.
It is impossible to add a new record in the StudentCode field which would be
number 08-1721. An error message follows: "The changes you requested to the
table were not suc-cessful because they would create duplicate values in the
index, primary key, or relation-ship, etc."
And more, the Autonumber field StudentID primary key indicates 386 instead
of 763!
Trying again had indicated 387, 388, etc. and it is still impossible to add
a new record.
On another working station, if one tries to enter a new record, StudentID
was 606! This Autonumber field gets all mixed up!
The back-end database IFTM_princip is located on a Windows Server 2003 and
the ta-bles on the front-end database IFTM are linked tables in each user.
The users work on individual workstations Windows XP.
The Msjet40.dll version is 4.0.9511.0
We installed the SP3, but the problem remains still the same.
Any ideas?
Thank you
P.S. However I realized that Access has accepted an autonumber whose record
had been removed. Would it be that Access does not like that record may be
removed in a table? There had been 42 records removed all together. I
checked those missing numbers. So the users will try to use them.