programming while database in use

K

Kevin

I am managing a database that is recently created and I will need to
continually make slight programming alterations as it is in use. If users
are in the database, and I wish to change something, I get the message: "You
do not have exclusive access to the database at this time....you may not be
able to save changes later..." or something like "...may be open by another
user..."

What is the best method for making changes to a database in use? Do I
create a backup copy, create or modify the objects I wish to, then have a
brief "blackout" period so I can paste the changed objects over to the one in
use? Or is it just best to have everyone stay out for a period of time while
I make the necassary changes?

Thank you in advance for any suggestions!
 
R

Roger Carlson

You will want to split it into a Front-End/Back-End (FE/BE) structure.
Basically, the FE/BE structure means that you have two Access.mdb's (or one
..mde and one .mdb) The front-end (.mdb or .mde) has all of the queries,
forms, reports, macros, and modules...everything but the tables. The
back-end (.mdb) has all the tables. The tables get linked from the back-end
to the front-end. For the most part, the application will work without any
changes.

There are several advantages of this approach:

1) You can work on an off-line copy of the FE while users continue to use
the application. If your application is not split, you cannot do this
because when you copy the code over, you also over-write the data as well.

2) As you noted, in Access 2000 and above, you cannot work on an application
if anyone else is in the database. Because of this, you HAVE to
have a split application because you must work in an off-line copy unless
you want to kick all your users off while you work.

3) This setup allows you to put the FE on the users hard drive, thereby
reducing network traffic and improving performance.

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
 
D

Douglas J. Steele

(PeteCresswell) said:
Per Kevin:

Separate the front end from the back end and work on your own copy of the
front
end linked to a test version of the back end.

When it's time to put your changes into production, re-link to the
production
back end and copy your new front end to wherever the users get to it.

As an aside, I'd say that it's also a lot better to put something in place
that
automagically copies that new version down to each user's PC where that
user
executes their own copy from C:\Temp or somesuch - and not have anybody
actually
executing the "mother" copy on the LAN server's drive.
Click to expand...

Like Tony Toews' free Auto FE updater, at
http://www.granite.ab.ca/access/autofe.htm
 
P

(PeteCresswell)

Per Kevin:
What is the best method for making changes to a database in use?
Click to expand...

Separate the front end from the back end and work on your own copy of the front
end linked to a test version of the back end.

When it's time to put your changes into production, re-link to the production
back end and copy your new front end to wherever the users get to it.

As an aside, I'd say that it's also a lot better to put something in place that
automagically copies that new version down to each user's PC where that user
executes their own copy from C:\Temp or somesuch - and not have anybody actually
executing the "mother" copy on the LAN server's drive.
 
Top