[AccessD] corrupt database - backup rather out-dated.

Hi Bill:

If you have your shadow copy setting on, on you working drive you can run a shadow copy backup of file that as still open...and then you can create a backup batch file, using the date/time as the file name via the computer's scheduler.  

http://www.runtime.org/shadow-copy.htm

Then you might want to try BitTorrent Sync as it can uses a shadow copy backup to synchronize directories between two computers on an incremental bases: http://www.bittorrent.com/sync

There is probably a few other solutions out there as well.

Jim 

----- Original Message -----
From: "Bill Benson" <bensonforums at gmail.com>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Sent: Monday, June 2, 2014 3:29:49 PM
Subject: Re: [AccessD] corrupt database - backup rather out-dated.

I tend to leave Access databases open too long while working on them.

Unlike an excel or word document, they change the on-disk version of the
data IMMEDIATELY with every data table change. I believe that is so even if
a database has been opened with exclusive access. So there really is no
stepping into the same river you stepped out of. This is to say that unless
you have a backup as part of your shutdown procedure, you cannot backup
"the same" database at any time after startup. You would have to do it as
an on disk operation with createobject
("scripting.filesystemobject").GetFile (Currentdb.name).Copy .... on
startup, but even then it might bear the current date not the date you last
closed the database.

Or not...
I am never quite sure what the date on disk means anyway.
On Jun 2, 2014 5:59 PM, "Jim Lawrence" <accessd at shaw.ca> wrote:

> Hi Bill:
>
> Some wise person said always make your backups automatic because you
> wouldn't remember.
>
> Jim
>
> ----- Original Message -----
> From: "Bill Benson" <bensonforums at gmail.com>
> To: "Access Developers discussion and problem solving" <
> accessd at databaseadvisors.com>
> Sent: Monday, June 2, 2014 1:44:45 PM
> Subject: Re: [AccessD] corrupt database - backup rather out-dated.
>
> I am happy to say that I did separate the data tables the program. Much of
> the advice given here is something that I already follow. However, it is
> true that if I had made a backup just some hours before that I would be in
> better shape than I am.
>
> I guess this could have been a thread about how to prevent the downside of
> this happening in the future. There are many such threads. However mainly
> this was a thread about a corrupt database and whether it could be fixed.
> Thanks all of those who offered help in this regard.
> On Jun 2, 2014 2:14 PM, "Gary Kjos" <garykjos at gmail.com> wrote:
>
> > That is certainly a good idea once you have the thing done but it can be
> a
> > pain during development as you may be adding fields and indexes and such
> > and having the data split up front can add work as you would need to
> > refresh links many times potentially.
> >
> > At least that is how I remember it from my develop for others days.
> >
> > GK
> >
> >
> > On Mon, Jun 2, 2014 at 1:06 PM, Jim Lawrence <accessd at shaw.ca> wrote:
> >
> > > Hi Gary:
> > >
> > > I would also add that it is a good idea to separate the actual data
> > tables
> > > from the rest of the application.
> > >
> > > Jim
> > >
> > >
> > --
> > Gary Kjos
> > garykjos at gmail.com
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com