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

Years ago we had a discussion here about using a hex editor on an Access
MDB file and copying parts of a working MDB file into a corrupted one in
order to make it good enough to be able to be opened and for code or
something to be extracted. It was a LONG time ago though and I don't recall
if it was actually successful or just a theoretical discussion.

GK


On Mon, Jun 2, 2014 at 3:44 PM, Bill Benson <bensonforums at gmail.com> wrote:

> 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