R
Ronald W. Roberts
I've got a student registration system that has been running about 10 years.
It's currently operates on Windows XP computers and in Access XP. It
operates on a network with a FE and BE databases with 4 or 5 users. There
have been no major program changes for over a year. The only changes have
been to reports changing bit map signature.
In July of 2007 the database experienced 2 problems were the system started
reusing AutoNumbers. It happen again twice, late fall, November or December
2007 and once in January 2008. It had always been a different table. I
aware of the problem Access has had with bad network cards causing this type
of problem. The Client's network people tell me there are no bad network
cards on the network. Prior to July 2007 old records were removed from the
system, but it did not leave any orphan records in the system
My questions are:
1.. Does the problem with bad network cards still cause this problem in
Access XP or 2003?
2.. Is there anything else that could be causing this problem?
3.. Could removing old records (records with a low AutoNumber) cause this
problem?
Thanks for any replies,
Ron
It's currently operates on Windows XP computers and in Access XP. It
operates on a network with a FE and BE databases with 4 or 5 users. There
have been no major program changes for over a year. The only changes have
been to reports changing bit map signature.
In July of 2007 the database experienced 2 problems were the system started
reusing AutoNumbers. It happen again twice, late fall, November or December
2007 and once in January 2008. It had always been a different table. I
aware of the problem Access has had with bad network cards causing this type
of problem. The Client's network people tell me there are no bad network
cards on the network. Prior to July 2007 old records were removed from the
system, but it did not leave any orphan records in the system
My questions are:
1.. Does the problem with bad network cards still cause this problem in
Access XP or 2003?
2.. Is there anything else that could be causing this problem?
3.. Could removing old records (records with a low AutoNumber) cause this
problem?
Thanks for any replies,
Ron