How can I export multiple forms etc.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a database which is used by about 30 users, all can input data into one table only, about 6 people can input data into all tables and 2 have permission to edit the design of the database.

The design of the database needs to be updated regularly (it is continually developing with new ideas), this creates a problem as all the other users need to exit the database to allow exclusive access to the person changing the design. I'm not sure how to get round this - in previous versions of Access design changes could be made to certain parts of the database as long as the users weren't in that part (but they could still use other parts of the database). In Access 2002 it doesn't allow this. The only solution i can think is to have a copy of the database - so that design changes can be made in one of them and the other users can have access to the other one. However, data may still be getting entered in the other database - therefore i would not be able to simply re-copy the one with design changes as data will be lost.

i was wondering if there is any way that i could copy all the queries/forms/reports etc. - but not the tables (unlikely that changes will be made to the tables anyway) without having to export them one at a time? Or alternatively is there any way of identifying all the items affected by design changes in one day and export only those items? (Kind of tracking the changes made throughout the day as a list at the end of the day)?

Any help would be good - or any other ideas on how to edit design whilst other users are still in the database.
Thanks.
 
ES,

The answer to: 'how to edit the design of an Access 2002 database while
others are it it' is pretty simple. It cannot be done.

The generally accepted "best practice" is to:

1. Split the database into a Front-End (FE) containing all Queries, Forms,
Reports, Macros and Modules and a Back-End (BE) containing the shared data
tables.

2. Distribute a copy of the front-end to each user's hard drive (FE will
link to tables in the BE). The BE will be located on the Server.

3. Keep a copy of the current FE stored on the server, so that you will
always have a back-up of the current "production version".

4. Do all of your development work on *your own* copy of the FE. This
keeps the current "production version" of the FE safe while you try out new
concepts, code, objects, etc. When you have completed all changes and
tested them, then you can deploy a new "production version" and distribute
it to users.

5. Distribution can be as simple as an email to users telling them to copy
from the server to their hard drives, to a short-cut to a batch file on each
user's desktop or an automatic updater, such as the one provided by Access
MVP Tony Toews as:

http://www.granite.ab.ca/access/autofe.htm


hth,
--
Cheryl Fischer
Law/Sys Associates
Houston, TX

ES said:
I have a database which is used by about 30 users, all can input data into
one table only, about 6 people can input data into all tables and 2 have
permission to edit the design of the database.
The design of the database needs to be updated regularly (it is
continually developing with new ideas), this creates a problem as all the
other users need to exit the database to allow exclusive access to the
person changing the design. I'm not sure how to get round this - in previous
versions of Access design changes could be made to certain parts of the
database as long as the users weren't in that part (but they could still use
other parts of the database). In Access 2002 it doesn't allow this. The only
solution i can think is to have a copy of the database - so that design
changes can be made in one of them and the other users can have access to
the other one. However, data may still be getting entered in the other
database - therefore i would not be able to simply re-copy the one with
design changes as data will be lost.
i was wondering if there is any way that i could copy all the
queries/forms/reports etc. - but not the tables (unlikely that changes will
be made to the tables anyway) without having to export them one at a time?
Or alternatively is there any way of identifying all the items affected by
design changes in one day and export only those items? (Kind of tracking the
changes made throughout the day as a list at the end of the day)?
Any help would be good - or any other ideas on how to edit design whilst
other users are still in the database.
 
Back
Top