The Access DB corruption isn't unique. But, it often is tied to a lack of a plan. It is not uncommon to see people trying to open up the combined front-end / back-end application from a network location. That will guarantee failure. It is like my IT support staff setting up SQL Server using the "recommended requirements". They had used that as the metric for why SQL Server wasn't any good. LOL MS doesn't do any better to warn about some basic Access setups.

My preference and suggested mode is to link Access Front-End to a SQL Server back-end database. There are so many advantages to SQL Server.

I am taking next week off to spend time with my son returning from his USMMA 300 days at Sea engineering internship.

The IT group told me this morning to prepare for Office 2013 in early Jan 2014.

You might ping this about mid Feb next year. I will set up some test to evaluate this once the newer versions are installed.

Also, this morning on my MAPS (MS partner) site, they are starting the new SQL Server - Excel add-in training.

Rather than cobble something together that is becoming obsolete, it will be worth waiting for the new.

For sure Sharepoint has gained popularity to distribute data. But, with any technology comes an overhead.

Your question brings up an interesting aspect to simplicity for managing records.

It is something I should look into after the New Year.

Sorry I can't spend more time on it now.