backup of database with multiple backend data bases

[Mark Kubicki]

I want to add a button to the main form that backs up 1 (ONLY) of 2 linked
databases...

It's a bit of an odd condition:
the way the project has been set up, it is linked to 2 backend databases;
fortunately, all of the tables in one mdb are prefixed [tbeTableName], and
in the other: [tboTableName]

I only want to backup those tables from the backend mdb [tbe...]; those
tables associted with the [tbo...] mdb do not need to be backed-up, nor do
those in the front end mdb

I am at a complete loss as to where to start, and ANY direction would be
greatly appreciated.
thanks in advance,
Mark

 

[John W. Vinson]

I want to add a button to the main form that backs up 1 (ONLY) of 2 linked
databases...

It's a bit of an odd condition:
the way the project has been set up, it is linked to 2 backend databases;
fortunately, all of the tables in one mdb are prefixed [tbeTableName], and
in the other: [tboTableName]

I only want to backup those tables from the backend mdb [tbe...]; those
tables associted with the [tbo...] mdb do not need to be backed-up, nor do
those in the front end mdb

I am at a complete loss as to where to start, and ANY direction would be
greatly appreciated.
thanks in advance,
Mark

Ummmm....

Back up the .mdb file itself.

There's little or no benefit to backing up individual tables. And there
ordinarily wouldn't be any tables in the frontend at all.

 

[Mark Kubicki]

i had presumed that i wouldbe backing up the entire mdb (withthe tbe...
tables); however, i'm looking for direction n how do do this. Everything i
find seems to want to backup the front end mdb...

I want to add a button to the main form that backs up 1 (ONLY) of 2 linked
databases...

It's a bit of an odd condition:
the way the project has been set up, it is linked to 2 backend databases;
fortunately, all of the tables in one mdb are prefixed [tbeTableName], and
in the other: [tboTableName]

I only want to backup those tables from the backend mdb [tbe...]; those
tables associted with the [tbo...] mdb do not need to be backed-up, nor do
those in the front end mdb

I am at a complete loss as to where to start, and ANY direction would be
greatly appreciated.
thanks in advance,
Mark

Ummmm....

Back up the .mdb file itself.

There's little or no benefit to backing up individual tables. And there
ordinarily wouldn't be any tables in the frontend at all.

 

[Douglas J. Steele]

An MDB is simply a file. You back it up the way you back up any other file.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

i had presumed that i wouldbe backing up the entire mdb (withthe tbe...
tables); however, i'm looking for direction n how do do this. Everything i
find seems to want to backup the front end mdb...

I want to add a button to the main form that backs up 1 (ONLY) of 2
linked
databases...

It's a bit of an odd condition:
the way the project has been set up, it is linked to 2 backend databases;
fortunately, all of the tables in one mdb are prefixed [tbeTableName],
and
in the other: [tboTableName]

I only want to backup those tables from the backend mdb [tbe...]; those
tables associted with the [tbo...] mdb do not need to be backed-up, nor
do
those in the front end mdb

I am at a complete loss as to where to start, and ANY direction would be
greatly appreciated.
thanks in advance,
Mark

Ummmm....

Back up the .mdb file itself.

There's little or no benefit to backing up individual tables. And there
ordinarily wouldn't be any tables in the frontend at all.

 

[John W. Vinson]

i had presumed that i wouldbe backing up the entire mdb (withthe tbe...
tables); however, i'm looking for direction n how do do this. Everything i
find seems to want to backup the front end mdb...

Do the backup *outside of Access altogether*.

You really don't want to back up an open Access database - you could grab the
backup right in the middle of an update operation, leaving it in an
inconsistant state or even corrupted.

Simply use your Windows backup software to back backend_1.mdb to some external
storage medium. It's best to be sure that nobody has the database open at the
time you do this.

 

[Paul Shapiro]

I would go further and say it's essential to be sure that no one has the db
open when you copy the .mdb. Without doing this often at all I have had
occasions where the copied file was corrupt and unusable when the copy was
made while someone had the .mdb open. Here's a simple batch file to only
make the copy of there is no .ldb file in the folder:

@echo off
REM Cannot make a valid copy while database is in use
if Exist \\Servername\Sharename\DatabaseName.ldb Goto DatabaseInUse
echo Copying DatabaseName.mdb to local disk
copy /y " \\Servername\Sharename\DatabaseName.mdb" "%HOMEDRIVE%%HOMEPATH%\My
Documents\Sharename\Backup\DatabaseName.mdb"
pause
exit

atabaseInUse
echo ERROR: Cannot copy database file while DatabaseName program is being
used.
pause
exit