Access corruption in windows 7

[rosatron20]

Our office is currently upgrading our machines to windows 7, previously we ran under windows xp and used access 2000 with call handlers using access 2000 runtime.

At the moment some have been upgraded to windows 7 with runtime 2003 and others are still on the old format. I admister the database and have access 2010.

Almost on a daily basis the database is being corrupt and needs to be repaired once everyone is out of it. I have been told several reasons as to possible causes but so far no solutions.

Any suggestions?

[ItsMe]

Are you experiencing something similar to this?

https://www.accessforums.net/access/...ned-40935.html

.

[NTC]

Access is extremely stable & mature and should never corrupt when in a proper configuration.

A multi user database must be a split database into 2 files with a single back end, and with each user having their own front end - and all front ends link to the single back end. A failure to implement a multi user application this way will guarantee corruption. That it did not corrupt when in xp/2000 is just a matter of luck.

The primary architectural difference between Access 2000 and Access 2007 (and beyond) is the move from the menu bar (which was eliminated) to the ribbon. This would render any code that calls a menu bar function to not work correctly. That is not corruption per se - but probably worth mentioning.