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

Jim Lawrence accessd at shaw.ca
Mon Jun 2 13:06:33 CDT 2014


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

----- Original Message -----
From: "Gary Kjos" <garykjos at gmail.com>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Sent: Monday, June 2, 2014 10:55:36 AM
Subject: Re: [AccessD] corrupt database - backup rather out-dated.

Well corruption can happen in all versions. I wouldn't personally blame
2013 version for your issues just yet. Could be. I just started using 2013
a couple weeks ago. I still create all my databases in 2000 format. I'm not
creating anything for distribution to others though.

I'd recommend you get a backup strategy/habit in place. Copy the file to a
ZIP file every day and copy that someplace other than the hard drive where
you are working or something like that. Loosing work during development is
never a good thing although I have found that sometimes being forced to
redo some things can lead to them being done in better ways the second time
through.

When I was developing databases for others with a lot of code I would
rename my work in progress database every day so I could always go back to
yesterdays version. Eventually I would have a dozen versions sometimes and
then I would delete all the early versions once I was sure I didn't need
them.

I also would make copies to other media or other systems too in case I had
a drive crash.

You can not have too many backups.

GK



> On Mon, Jun 2, 2014 at 12:37 PM, Bill Benson <bensonforums at gmail.com>
> wrote:
>
>> Thanks Jim.
>>
>> I am fortunate to learn of this problem early. I have never had this
>> happen
>> in earlier versions (2010 on back to 97) and I don't think this bodes well
>> for my love of 2013. I will probably put 2010 back and uninstall 2013.
>> On Jun 2, 2014 8:00 AM, "Jim Dettman" <jimdettman at verizon.net> wrote:
>>
>> >
>> >  Unfortunately Microsoft never updated the JETCOMP.EXE tool for the
>> .accdb
>> > format.
>> >
>> >  It was the only tool that would work (sometimes) in situations like
>> this
>> > because unlike the compact and repair, it would not open the DB as a DB
>> > first, but treat it just like as a file and repair the DBH (Database
>> > Header)
>> > page first, then open the DB.
>> >
>> >  If you can't open it, you don't have any options other than a recovery
>> > service out on the net.
>> >
>> > 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


More information about the AccessD mailing list