A client has a heavily-used AC2003 networked app running on a server for the past 10+ years. Gradually, some users upgraded to AC2007 and AC2010 without problems.
Recently however, several of the users of this particular app were upgraded to 2013 and since then, we have experienced weekly database corruption. It's not unusual for 3-6 users to simultaneously be updating the same table; and typically these users are a mixture of the 4 versions of MsAccess.
"Splitting out" the program into a front-end/back-end has not helped (may have made it worse)....seems to be the back-end (....Data.mdb) now that is getting corrupted.
Client has placed an order for all new workstations which will come with 2013, I assume; but these will likely not be installed until later in Q1 2014.
Can anyone think of anything a developer can do under these mixed-version conditions, while waiting for the total 2013 switchover?
Sorry so long-winded -- trying to reduce questions up front....
Thanks in advance.