This is what I do and have not had any problems
frount End (Screen/Querys/reports)
Put the BackEnd on the Server
then in the Frount End I Map the Table by \\servername\MSdata$\data.mdb
this way i don't have to map the drive (what user can not see can't delete)
I copy Screen the user computer
this also cut down on the network traffle
Knock on wood I have not had a problem with this setup in the last 6 year.
the only down side is the Updateing of the screens
I have 2 ways of doing this
1. I have a VB program a menu system that check the server for updates
2. in the startup I use to have a Batch file that would copy the file from the server to the user computer.
hope this help
the aim is store once, not store multiple times
Remember... Optimize 'til you die!
Access based on my own environment: DAO3.6/A97/A2000/A2003/A2007/A2010
VB-NET based on my own environment started 2007
SQL-2005 based on my own environment started 2008
YOUR PASSWORD IS JUST LIKE YOUR TOOTHBRUSH DON'T SHARE IT.
DONT WORRY ABOUT THOSE WHO TALK BEHIND YOUR BACK
THEY'RE BEHIND YOU FOR A REASON