Access can definitely be prone to corruption in a multi user environment, although I don't think the multi use part is what caused your issues. It (like many applications) can corrupt if not shut down properly. My biggest tip to avoid user caused corruption is to force a lot of saves for the user. In my travels my biggest corruption casue is when two users try to change the same record.
Here is some code to a .vbs script that I wrote tat is used to automate a backup. I then set a scheduled task to run this once a day. All you have to do is change the 3 variables (two path names, one db name) to your values.
Dim wsh
Dim MyNetworkPath
Dim FSO
Dim MyLocalPath
Dim MyDB
Dim dCurrent
'this utility makes a backup copy of the db and renames with a date stamp.
'the utility is run daily through a scheduled task.
dCurrent= DatePart("YYYY", Date) & DatePart("M", Date) & DatePart("D", Date)
'the variables
MyNetworkPath = "P:\some_path\on_your_network\" 'static path of the database on the network (to copy)
MyLocalPath = "P:\some_other_path\on_your_network\where_the_backup_goes\" 'static path of the copy on the network (where the copy goes)
MyDb = "My_DB.mdb" 'current database name (to copy)
Set wsh = CreateObject("Wscript.Shell")
Set FSO = CreateObject("Scripting.FileSystemObject")
FSO.CopyFile MyNetworkPath & MyDb, MyLocalPath & left(MyDb,len(MyDb)-4) & dCurrent & ".mdb"
Set wsh = nothing
Set FSO = nothing
Bookmarks