Darryl Collins
darryl at whittleconsulting.com.au
Tue Jun 3 18:25:36 CDT 2014
Yeah, Not saying this for you Bill, I know you have been around long enough to know this stuff and just got unlucky (as well all have at some point). When I do MS Access Dev work I usually just save a zipped copy a few times a day. This has saved my bacon numerous times. MS Access does tend to crap out randomly from time to time. Usually you can recover it by just importing everything into a new empty shell, but in some cases, includings Bill's, it is toasted and you need to start from scratch / backup / memory or whatever. Cheers darryl -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence Sent: Wednesday, 4 June 2014 12:37 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] corrupt database - backup rather out-dated. Hi Bill: Hate to say it, but every programmer has to go through this right-of-passage. These are mistakes you make once in your career but with a bit of luck and effort you should recover in fine form. Now you will remember the three main tasks you do as a developer; backup, backup and backup. 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 11:27:03 PM Subject: Re: [AccessD] corrupt database - backup rather out-dated. I believe the corruption occurred when my battery fully drained while in sleep mode, or else when Windows Update forced a reboot at it's regular 3AM destroy all user's work stealth settings brought to you by micro-scoff. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Tuesday, June 03, 2014 2:24 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] corrupt database - backup rather out-dated. Hi Gary That was doable for some cases where the header had been overwritten by some malfunctioning cache or network error. Such a file was not reparable by the repair routine. The simple trick was to find the latest backup or create a new database, copy the header pages from this, and paste it over the header of the corrupt database file. I haven't seen this kind of error for years. Networks have improved. /gustav -----Oprindelig meddelelse----- Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af Gary Kjos Sendt: 2. juni 2014 22:58 Til: Access Developers discussion and problem solving Emne: Re: [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 -- 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