Backing up data from mde to mdb file

[Guest]

Hi,

I have a question regarding data backup. Currently, I have an .mdb file I
keep in a personal file where I make changes to the functionality, appearance
etc. of the database. I have an .mde file on a common directory for multiple
users.

Each day I import the data from the .mde file into the .mdb file as a backup
measure. I'll also do this before rebuilding the .mde file if any changes
are necessary. It seems to work well - except I lose my table relationships!
I've come to the point where I've realized how much time these relationships
can save, and I don't want to have to recreate them everytime I import the
current tables.

Is there an easier way to update the data and maintain the relationships?

Thanks!

Sean

 

[Guest]

Hi, for our backup we simply 'copy' the entire mdb file rather than import
tables......we tag on a date to the file name so that we end up with multiple
copies (by date) and then eventually delete the older ones.... just something
to consider.

 

[Guest]

The main reason is that there are occassional changes/improvements being made
in the mdb file. By importing the mde tables into the mdb file, I know I
won't lose any data when rebuilding the mde. It looks like using this
strategy means I will have to re-establish the relationships whenever I do
this! I think I might try splitting the database into front and back ends.
I haven't tried this before, but from what I've read it might solve the
problem better than importing/updating tables!

 

[Guest]

I do this sometime as well, but the big part of the issue is having an mde
file and an mdb file I would like to keep up to date. I think I'll try
splitting the database, then I can simply backup the file containing the
tables based on your suggestion below. Thanks!

 

[Guest]

I think I've found a way to make this work and thought I'd share it here in
case anyone else is interested!

1. I started with an Access97 file (not really relevant to the topic) and
converted to Access 2003 format.
2. The database was split into a back end and a front end.
3. The table relationships were built in the back end.
4. An mde file was created from the front end.

Now, I backup the data by simply copying and saving the entire back end
file. And I maintain my ability to keep a stable (mde) front end environment
that is easy to update from the master mdb.

SM

 

[Larry Daugherty]

You should split your application (MDB) into a Front_End which
includes everything but the tables and the Back_End which includes
just the tables. Then, just make the FE an MDE so that the users
can't be twiddling with your design and leave the BE as an MDB. Now,
the only time you'll have to mess with table data is when your table
design changes.

For splitting your application, look in Access Help for "Split"

For best results, put the BE on the common share and give each user a
copy of the FE.

The next logical question is "How do I keep the users' files current.
If there are only a couple of knowledgeable users you can handle it by
emailing them the new MDE with instructions to delete the old one and
replace it with the one attached. If you have a lot of users you may
want to look into Tony Toews FEUpdater. It's a freebie Tony developed
to handle the situation that requires a little work to tailor to your
application.

HTH