Access DB: one copy with new data, other with new code

  • Thread starter Thread starter Mark G. Meyers
  • Start date Start date
M

Mark G. Meyers

I want to be able to create and work on an access db that will be used by
someone remotely, where we will not be connected.

So during that time I would like to be able to add fields and tables, forms
and code, and to simplify the process of getting the data from the other
copy into mine, and then redstribute the new db with all code and data
together.

Where should I look?
 
There are a number of possible approaches to this, but my own preferred
method is as follows.

First, split the application from the data - one 'back-end' data MDB
containing only the tables, one 'front-end' application MDB containing
everything else and linking to the tables in the data MDB.

When you send out the new version, send an empty copy of the new data MDB.
Make sure you give it a different name, and/or install it into a different
folder from the old data MDB, so as not to overwrite the old data.

Provide a feature in the new application to import the data from the old
data file into the new one.

An alternative is to use either DAO code or DDL queries in the new
application to modify the structure of the existing data file.
 
Back
Top