Backing Up Access Databases

[Guest]

Access 2003. Is there a way to backup an Access database whilke it is open?
Is there a way to backup the database programmatically (from a macro or
module)? Thanks for any help.

 

[Guest]

Tools-->Database Utilities-->Backup database.

You can also record this menu path in a macro and assign it to a button.

 

[Guest]

What does backup do when you have the database split into frontend and
backend? Do I need to run a separate backup on each piece?

 

[Guest]

How do I assign the menu path to a button? Can you give me an example or a
hint? Thanks.

 

[Guest]

Excellent questions. Backing up is very good. And your question about a split
database is spot on. If you compact and repair the FE, it does nothing for
the BE.

Option 1: Put the BE on a network drive and make sure that this drive is
backed up frequently to tape or another drive.

Option 2: Schedule a Window Scheduler job to make a copy of the database
files and put them on another physical drive on the network or to a PC's
drive. As long as this is done when the database isn't in use, this will
work. Of course the PC may need to be left on.

Option 3: Do both Option 1 and 2 to be double sure that you have a good
backup.

Option 4: Copy the database files to something like a flash drive when the
thought strikes you.

Backups are like seat belts. Worthless and a bother until the moment that
you need one. Then they are priceless.

 

[Guest]

I would create a form with a button on it.

Then record a macro in which you go through the process of accessing 'Backup
Database' via the menu path I give below, save that macro and make a note of
its name.

Then go back to the form with the button on it, right-click on the button
and select assign macro. Then choose the macro you just recorded.

This should then allow you to click a button and have the db backup.

There may a more elegant, code-based way of doing this, so that the db can
update automatically at a set interval. I'm not sure how to do that, though.

 

[dbahooker]

use Access Data Projects, MDB is for ****ing dipshits and babies.

SQL Server; you can backup and restore-- on a scheduled basis-- without
a single line of code.

MDB is for losers. MDB has been obsolete for almost 10 years now.

lose the training wheels.

Start teaching your inmates about SQL Server... if you want to really
make a difference.

I've been in jail. Maybe a half-dozen times.

None of your daisy-hippie bullshit is what saved me.

it's not talking about your feelings that saves people from jail.
Having a viable career path is what keeps people on the straight and
narrow.

-Aaron
Convict

 

[dbahooker]

dont ever run MDB across a network; performance is unacceptable; and
stability is a joke.

Access isn't smart enough to handle running across a network.

 

[dbahooker]

and again, Jerry?

if you weren't a flaming pussy, then maybe you wouldn't make your
customers choose between light, cheap and strong.

i dont make my customers make that choice; I provide ALL THREE-- LIGHT
CHEAP AND STRONG.

Lose the training wheels, Jerry.

-Aaron

 

[dbahooker]

the answer is to use

ACCESS DATA PROJECTS.

MDB is for retards and idiots.

-Aaron

 

[Steve Schapel]

Dave,

Are you talking about Microsoft Access here? "Record a macro" isn't
really an Access concept - I don't know what that means. Similarly,
there is no "assign macro" item on the right-click menu of command
buttons. Have you tested the approach you are suggesting?

 

[dbahooker]

YES.. BUT IT SHOULD BE A FEATURE!!!

Dave,

Are you talking about Microsoft Access here? "Record a macro" isn't
really an Access concept - I don't know what that means. Similarly,
there is no "assign macro" item on the right-click menu of command
buttons. Have you tested the approach you are suggesting?