Will record corruption stop if I split?

[Guest]

My Acces 2003 database is used simultaneously by several people, but it is
not split. Could this be the reason for Error 3709 which
happens when a user is editing a record via a form and the record suddenly
corrupts to show rubbish data? After this, you cannot edit or delete the
record any more.
I suspect this happens when one user is editing a record which then gets
called by a select query being executed by another user. Am I right? This
error started occuring recently, since I added several options to the
switchboard that run macros to execute multiple select queries.

Is splitting the database the answer? If not, any other suggestions, please?

Thanks.
Ewa

 

[Rick Brandt]

My Acces 2003 database is used simultaneously by several people, but
it is not split. Could this be the reason for Error 3709 which
happens when a user is editing a record via a form and the record
suddenly corrupts to show rubbish data? After this, you cannot edit
or delete the record any more.
I suspect this happens when one user is editing a record which then
gets called by a select query being executed by another user. Am I
right? This error started occuring recently, since I added several
options to the switchboard that run macros to execute multiple select
queries.

Is splitting the database the answer? If not, any other suggestions,
please?

Proper food handling does not gurantee that you will never get sick from your
food, but it greatly decreases the likelyhood. Splitting your app and data
corruption have the same relationship.

Anything that disrupts your connection to the data during a write can corrupt
the file. The odds of that happening are much higher if you have multiple
people in the same front end.

 

[Guest]

What Rick said. I'll add the following:

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Guest]

Thank you, that's helpful.
Ewa

Proper food handling does not gurantee that you will never get sick from your
food, but it greatly decreases the likelyhood. Splitting your app and data
corruption have the same relationship.

Anything that disrupts your connection to the data during a write can corrupt
the file. The odds of that happening are much higher if you have multiple
people in the same front end.

 

[Guest]

Thank you for all the links - I will follow them up,
Ewa

 

[Pat Hartman \(MVP\)]

And in addition to the other good advice, avoid macros in a "production"
application. They do not support error handling and what you are
experiencing might be easily trappable if you use VBA.