Re: Corrupt Access File
- From: "'69 Camaro" <ForwardZERO_SPAM.To.69Camaro@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 18 May 2007 12:06:27 -0700
PMFBI:
You said there is no easy way. Is there a hard way?
Yes. Can you program binary, and do you have the specifications for the Jet
database file format so that you can check each bit for what it's supposed
to be? The "hard way" is fairly difficult and time consuming, and just not
worth it. If database corruption is common enough in your environment, then
you need to address what is causing the corruption and eliminate it or else
migrate to a more robust database, such as Oracle or SQL Server.
And determining that the file size isn't a multiple of 4,096 bytes (the size
of each data page) is only one determiner of file corruption, and not a very
common one at that. It happens when the database file has been saved in
another file format by a different application and certain data is
reformatted, removing some of the bytes from what was intended to be a
complete database page in the Jet file format.
HTH.
Gunny
See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
.
- Follow-Ups:
- Re: Corrupt Access File
- From: DS
- Re: Corrupt Access File
- References:
- Corrupt Access File
- From: DS
- Re: Corrupt Access File
- From: '69 Camaro
- Re: Corrupt Access File
- From: DS
- Re: Corrupt Access File
- From: John W . Vinson
- Re: Corrupt Access File
- From: DS
- Re: Corrupt Access File
- From: John W . Vinson
- Re: Corrupt Access File
- From: DS
- Corrupt Access File
- Prev by Date: Re: Corrupt Access File
- Next by Date: Re: Corrupt Access File
- Previous by thread: Re: Corrupt Access File
- Next by thread: Re: Corrupt Access File
- Index(es):
Relevant Pages
|