Table Corruption

[Guest]

I'm having some difficulty with a seemingly
corrupted backend. I've got a split configured application used by a client
of mine. One of the features I've got implemented is periodic backend
compression. When exiting the client, the program checks a date that I have
stored in a table on the backend. If 3 weeks have elapsed between the stored
date and now(), I advise the user that the backend will be compressed. The
program then makes a backup copy of the backend - stores the current date -
then compresses it. Every once in a while, data in tables gets skewed. When
adding new records, data gets plugged into incorrect fields. Does anyone know
what causes this and if there's anything that can be done? Thanks in advance.

Bnielsen

 

[Nick Coe \(UK\)]

If you are running the compact/repair from a client
workstation onto the fileserver that can sometimes cause
problems. Much better to run compact repair on the server
machine itself.

Also make certain that all users are logged off and every
front end is closed.

--
Nick Coe (UK)
http://www.alphacos.co.uk/
pAnimal - Pedigrees and Breeding - Download free 30 day
trial
AccHelp - Skeleton Help for Access Apps
http://www.pjandcoe.co.uk TShirts with Bark factor...


In Bnielsen typed:

 

[Tony Toews]

If you are running the compact/repair from a client
workstation onto the fileserver that can sometimes cause
problems. Much better to run compact repair on the server
machine itself.

FWIW I've hardly ever had a problem running a compact and repair from
a file share. Also many system admins won't, understandably, want
Access or any software for that matter installed on the server.
Finally sys admins don't want users to be able to log onto the server
either.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[liuwen]

I'm having some difficulty with a seemingly
corrupted backend. I've got a split configured application used by a client
of mine. One of the features I've got implemented is periodic backend
compression. When exiting the client, the program checks a date that I have
stored in a table on the backend. If 3 weeks have elapsed between the stored
date and now(), I advise the user that the backend will be compressed. The
program then makes a backup copy of the backend - stores the current date -
then compresses it. Every once in a while, data in tables gets skewed. When
adding new records, data gets plugged into incorrect fields. Does anyone know
what causes this and if there's anything that can be done? Thanks in advance.

llllll