Repair and Compact Issues with Access 97

[PamelaDV]

I am running into big problems with my Access 97 databases. I have
one database in particular that needs to be repaired and compacted
several times a day. I have problems when doing a repair and compact
where it doesn't get all the way through the process and I end up
having to manually rename the db1.mdb that is created during the
process. I am wondering if you all think that this is an issue with
Access 97 (meaning that we should upgrade to a more recent version of
Access), or could this be a network issue? The company that I work
for is a bit behind the times and Access 97 is the standard for Access
Development work. I am currently trying to convince them that it is
time to upgrade. Do you think that these problems that I'm having are
related to the fact that we are still using Access 97 while the
company is upgrading their operating systems to Win2K? Or is it
possible that there is a network issue here? I am not on the network
team and they aren't being very helpful when I ask questions. The
standard answer is "There is no problem with the network. It must be
an Access problem." Whatever. I have re-written and optimized the
databases in question and there is no reason for the back end data to
be corrupting on a continual basis. So then I ask to upgrade to at
least Access 2000 if not XP and I am told there is no money for that
right now. So are my hands tied?

[Jeremy Wallace]

No, this is probably not an A97 issue. That's quite a stable release.
Network issues and dumb users are probably more the issue. Is the database
split into a front end and a back end? Are users trained to exit databases
before shutting down their machines? Often a single flaky network card can
be responsible for repeated corruption.

Check out Tony's page on corruption:
http://www.granite.ab.ca/access/corruptmdbs.htm
--
Jeremy Wallace
AlphaBet City Dataworks
http://www.ABCDataworks.com
"PamelaDV" <pd******@steelcase.com> wrote in message
news:b6*************************@posting.google.co m...

I am running into big problems with my Access 97 databases. I have
one database in particular that needs to be repaired and compacted
several times a day. I have problems when doing a repair and compact
where it doesn't get all the way through the process and I end up
having to manually rename the db1.mdb that is created during the
process. I am wondering if you all think that this is an issue with
Access 97 (meaning that we should upgrade to a more recent version of
Access), or could this be a network issue? The company that I work
for is a bit behind the times and Access 97 is the standard for Access
Development work. I am currently trying to convince them that it is
time to upgrade. Do you think that these problems that I'm having are
related to the fact that we are still using Access 97 while the
company is upgrading their operating systems to Win2K? Or is it
possible that there is a network issue here? I am not on the network
team and they aren't being very helpful when I ask questions. The
standard answer is "There is no problem with the network. It must be
an Access problem." Whatever. I have re-written and optimized the
databases in question and there is no reason for the back end data to
be corrupting on a continual basis. So then I ask to upgrade to at
least Access 2000 if not XP and I am told there is no money for that
right now. So are my hands tied?