M
m galvin
How can I make this automatic when the db is closed?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Stephen Raftery
One way might be to call the db from a batch file, and end the batch file
with a call to your backup program.
Another possibility might be to put a line in the Close event of your
Switchboard form which calls the backup program when the form closes.
with a call to your backup program.
Another possibility might be to put a line in the Close event of your
Switchboard form which calls the backup program when the form closes.
T
Tom van Stiphout
On Fri, 2 Apr 2010 08:26:02 -0700, m galvin
You can use the Windows Scheduler to schedule a task to perform the
backup. In most companies that's done overnight.
-Tom.
Microsoft Access MVP
You can use the Windows Scheduler to schedule a task to perform the
backup. In most companies that's done overnight.
-Tom.
Microsoft Access MVP
M
m galvin
When you say "which calls the backup program when the form closes", would
this be via code or possibly a macro? If code, what would the code be?
this be via code or possibly a macro? If code, what would the code be?
D
Daniel Pineault
The key thing to remember when performing a backup is that no one can be
using the database at the time or the backup may end up corrupt.
As such, as Tom mentioned, using a bacth file in conjunction with the Task
Scheduler can be a good approach. Perform your backup when 99.9999% chance
that no one will be using the db (say 2:00am).
Below is a good post on the subject (batch file code)
http://groups.google.ca/group/micro...ba8/380f102d443e52df?hl=en&q=ms+access+backup
Another approach using vba code within your database is viable also, a good
source for this can be found at
http://www.pointltd.com/Downloads/Details.asp?dlID=49
--
Hope this helps,
Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.
using the database at the time or the backup may end up corrupt.
As such, as Tom mentioned, using a bacth file in conjunction with the Task
Scheduler can be a good approach. Perform your backup when 99.9999% chance
that no one will be using the db (say 2:00am).
Below is a good post on the subject (batch file code)
http://groups.google.ca/group/micro...ba8/380f102d443e52df?hl=en&q=ms+access+backup
Another approach using vba code within your database is viable also, a good
source for this can be found at
http://www.pointltd.com/Downloads/Details.asp?dlID=49
--
Hope this helps,
Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.
J
Jeff Boyce
If, by "data base", you mean the data itself, rather than the front-end,
using a split design and placing the back-end on your organization's LAN
might be a way to have your LAN administrator be responsible. The LAN at my
organization is backed up automatically...
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.
using a split design and placing the back-end on your organization's LAN
might be a way to have your LAN administrator be responsible. The LAN at my
organization is backed up automatically...
Regards
Jeff Boyce
Microsoft Access MVP
--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.
Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.
You can thank the FTC of the USA for making this disclaimer
possible/necessary.