Quote:
Originally Posted by kate2272
(1) despite the database being in a public folder, it isn't allowing other users to access it
Have you split your database? In a multi-user environment the database should split into a front end (with forms, reports, queries, etc) and a back end (with tables.) Having an un-split database on a shared is a sure fire way to generate all kinds of problems including chronic corruption. Access can do this for you automatically.
A copy of the front end should be on each user's PC.
A single copy of the back end should be on the shared drive.
Quote:
Originally Posted by kate2272
(2) when the database is exited it automatically backs up ... so by the end of a day there could be up to 20 backed up copies.
I know of no native facility in any version of Access, certainly not up thru 2003, that allows for the automatic backup of a db on exiting. There has to either be code in the database for doing this or, I suppose, maybe your IT administrative people have something set up in your network that does this.
What exactly does "implemented" mean in this context? Did you develop the db yourself, or was it developed by someone else and you're simply getting it up and running? IF the former, did you do it from scratch or did you use another database as a template? I ask because that may be the source of the code that is backing up it up.