Making changes to back end

[Slez via AccessMonster.com]

I need to make changes to the back end of a database that is in use. For the
sake of minimizing downtime, is this my best approach?

1. Make a copy of both the back end and the front end and reset the links
between the copies.
2. Work on modifications to tables in the copy BE and forms/reports in the
copy FE.
3. Set up a "blackout" period to copy/apply the changes from the copies to
the original BE and FE.
4. Distribute new FE to user's local drives.

To the best of my knowledge, design changes cannot be made while users are
accessing the BE, but I thought I'd ask for some comfirmation of my planned
approach. I appreciate any opinions!
Thanks!

 

[Jeff Boyce]

You might want to take a look at Tony T's website for information about an
autoloader routine to refresh FEs. (www.granite.ab.ca/access)

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[mscertified]

Your approach will work but bear in mind that any data changes, between
making your BE copy and implementing your BE changes, will be lost. Sometimes
you can get away with just importing the changed objects rather than doing a
complete copy.

-Dorian

 

[Klatuu]

My preferred way to update a BE is to use Jet SQL Data Definition commands to
make changes. Where I am, I have over 400 back ends to the same front end.
The user selects an mdb by selecting a client. It has to be this way because
the data would not fit in one mdb.

So, I wrote a back end updater that loops through all the mdbs for the app
and makes the modifications to the tables. I run it from Task Scheduler at
1:00 AM on Sunday. Now, that takes care of the tables. If you have anything
other than tables and relationships in the BE, you are doing it wrong <g>

 

[Slez via AccessMonster.com]

I guess my intent was to just import the changed objects because I will
primarily be adding tables/fields. I'm only eliminating one field so I can
just transfer that data into the new fields/tables. I just wanted a complete
copy to ensure all of my forms and reports worked properly.

Thanks to all for the responses!...Good stuff!
Slez

Your approach will work but bear in mind that any data changes, between
making your BE copy and implementing your BE changes, will be lost. Sometimes
you can get away with just importing the changed objects rather than doing a
complete copy.

-Dorian

I need to make changes to the back end of a database that is in use. For the
sake of minimizing downtime, is this my best approach?

[quoted text clipped - 11 lines]

approach. I appreciate any opinions!
Thanks!