It's far simpler than you think. You shouldn't have multiple users in a single mdb file anyway, so splitting should be done.
Backend - mdb file that contains just the tables/relationships.
Frontend - all other objects, and linked tables (linked to the tables in the backend).
You put the backend on the server where everyone has access. Give each user a copy of the frontend on their local PC.
You can use the splitter wizard to do it or it's easy enough to do yourself.
With everyone out, make a copy of your mdb. Put this copy on the server and rename it e.g. if it's called 'Copy of Design.mdb' rename it to Design_be.mdb.
Open this mdb and delete all the objects, except the tables. Compact it and close.
Open your original mdb and delete the tables. Use File, Get External Data, Link Tables and navigate to the location of the backend on the server (hint, use My Network Places to locate it and it'll use the UNC pathnames, and you don't need to be concerned about users having different mapped drives). Select All, and OK.
Next you just need to copy this 'frontend' to each user. When they open the frontend they'll be connected to the tables in the backend on the server.
--
Joan Wild
Microsoft Access MVP
: Hi Joan,
:
: Thanks for the reply. I was afraid of something like that. I am fairly new
: to Access and the concept of front-end and back-end. But I am guessing that
: implies coding a front-end, that allows the user to only see certain data
: (through forms) and run certain queries through designed controls/menus.
: Since this is supposed to be a temporary solution, I'm trying to avoid a lot
: of coding.... Is it possible to get a front-end with minimal coding involved?
: (I'm thinkingwe could design a front-end for the stable part; and only go
: into the development database when we want to add queries)
:
:
:
: "Joan Wild" wrote:
:
: > You can implement security, but since you are all creating queries, it could get a bit messy. Why not leave these queries in the production mdb, and give each user a separate frontend, linked to the backend tables. They then can use this separate frontend for adhoq queries. If someone produces something that everyone needs, you can then import it into the production database.
: >
: > --
: > Joan Wild
: > Microsoft Access MVP
: > : We have an access database that we use to prepare reports, by running a bunch
: > : of queries in succession. All of us have access to the database window,
: > : because we all add new queries to create new reports.
: > : Once the reports are created, the queries typically won't and should not
: > : change (i.e., the design/SQL code itself).
: > : We'd like to be able to lock these queries from any changes so that we avoid
: > : making a change by misstake (there are only 3 users/developers of this
: > : database, so the risk is not that high - but it does exist).
: > : Is there a way to lock an individual query's design? or what are suggested
: > : alternatives?
: > :
: > : Thanks,
: > :
: > : Vanessa
: >
