Per Chip:
I have an Access 2003 front end and backend. One user (company VP) has 2007
installed. He insists on opening the network front end instead of making a
copy. Since he started doing this the front end is corrupting. First, code
would stop. Then all forms, reports, and modules were gone. Now the MSysAces
table is missing. I am hoping that demanding he copy the front end will solve
the issue. Any other thoughts?
Letting users open a front end over the LAN is bad juju.
My personal mojo is a .Bat file.
Our users don't even know where the GoldCopies of their
applications live, but if they did, I'd make those directories
ReadOnly for them.
Each user has an icon on their desktop that's aimed at the .Bat
file. When the .Bat file runs, it checks to see if the latest
version is on the user's C: drive. If so it just opens it. If
not, it copies the latest-and-greatest down and then opens it.
Installing one of our apps on a user's desktop consists of two
one-time-only actions:
--------------------------------------------------------------
- Verifying that their install of MS Office includes MS Access
and updating it if necessary.
- Copying the icon from a LAN directory to their desktop
--------------------------------------------------------------
Maybe I'm just stuck in a rut or something, but to me this is the
Good-Right-And-Holy-Path for deployment of MS Access apps.
Greater minds than mine have crafted special applications to do
the what my .Bat file does and one of them would probably be the
path of least resistance.