AllExperts > Using MS Access 
Search      
Using MS Access
Volunteer
Answers to thousands of questions
 Home · More Using MS Access Questions · Answer Library  · Encyclopedia ·
More Using MS Access Answers
Question Library

Ask a question about Using MS Access
Volunteer
Experts of the Month
Expert Login

Awards

About Us
Tell friends
Link to Us
Disclaimer

 
 
 
 
About Scottgem
Expertise
I can answer almost all types of questions relating to Microsoft Access usage and application design. My strengths are database and interface design.

Experience
I've been designing databases for over 15 years working with dBase, FoxPro, Approach and Access.

Organizations
Author of Microsoft Office Access 2007 VBA
Techncial Editor for Special Edition Using Microsoft Access 2007 and Access 2007 Forms, Reports & Queries From Que Publishing

 
   

You are here:  Experts > Computing/Technology > Business Software > Using MS Access > Merging, Updating Database

Using MS Access - Merging, Updating Database


Expert: Scottgem - 6/29/2009

Question
I have a database in use at the place in which I work.  It's constantly being updated and changed.  I'm starting to develop new features for the database...new forms, new code.  When I come in, I need to update the database.  But what's the best way to do this??  I don't think there's a merge feature?  I'm a little lost at how I might update the database during development.  Such as table fields, and updated forms...

How is this done in the professional environment?

Also keep in mind, in the near future, I'd like to run the Access database completely on the Access runtime with a package installer.  Any ideas how to update from this as well?

Any help would be great...

Answer
First, you need to split the database. All the tables go in the back end and everything else is in the front end. EVERY database that has multiple users (including a developer and a user as different people) NEEDS to be split. There is no way you can maintain the database otherwise. Also a non split database is an invitation to corruption.

Most changes to a production database occur in the front end, so the developer maintains their own copy of the front end in a development folder. It's easy to replace the front end whenever there are changes. There are several autoupdaters avaiable as freeware.

If, however, you need to make changes to the back end, that is more complex. If the back end resides on a network share (the front ends should be installed locally) then you may need to make those changes at off hours or when you can force the users out of the database.

Hope this helps,
Scott<>
Microsoft Access MVP 2007
Author: Microsoft Office Access 2007 VBA


Add to this Answer   Ask a Question


 
User Agreement | Privacy Policy | Kids' Privacy Policy | Help
Copyright  © 2008 About, Inc. AllExperts, AllExperts.com, and About.com are registered trademarks of About, Inc. All rights reserved.