Can I Recovery a corrupted database ("unrecognized database format") ?

[antonioromera]

Exist any utility to recover Microsoft Access databases ?<br>&quot;unrecognized database format&quot; error when open, compact<br>or repair corrupted database.<br>The database was damaged in unexpected computer power off.<br>I'm a spanish programmer. Sorry. My english is very bad.<br>Thanks.<br>Antonio Romera.

 

[xtreme1]

Yes, that is usually repairable.&nbsp;&nbsp;I encounter that problem more often than I would like.&nbsp;&nbsp;If the database is stored in multiple .MDB files, which I assume it is, try opening each of those files separately.&nbsp;&nbsp;When you encounter the file that is having problems it should pop-up a message telling you the file is damaged in some way, and will ask you if you'd like to try to repair it.&nbsp;&nbsp;Respond yes to this, and all should go well.&nbsp;&nbsp;Be sure no one is trying to access the database at the time of repair, or it won't be able to do it.&nbsp;&nbsp;It's been my experience that that type of error is harmless 99% of the time, besides being an annoyance.&nbsp;&nbsp;Good luck..=] <p>xtreme1<br><a href=mailto:rbio@excite.com>rbio@excite.com</a><br><a href= > </a><br>

 

[DougP]

If you make a .MDE file your corruption problems wil go away.<br><br>See My FAQ's on that:<br><br>Why do I need an .MDE<br><A HREF="

http://www.tek-tips.com/faq.cfm?spid=181&page=1&CFID=4281248&CFToken=4471053#91"

TARGET="_new">

http://www.tek-tips.com/faq.cfm?spid=181&page=1&CFID=4281248&CFToken=4471053#91</A><br><br>How

do I make one<br><A HREF="

http://www.tek-tips.com/faq.cfm?spid=181&page=1&CFID=4281248&CFToken=4471053#90"

TARGET="_new">

http://www.tek-tips.com/faq.cfm?spid=181&page=1&CFID=4281248&CFToken=4471053#90</A>

<p>DougP<br><a href=mailto: dposton@universal1.com> dposton@universal1.com</a><br><a href= > </a><br> Ask me how Bar-codes can help you be more productive.

 

[Sam63]

Can you use a VB6.0 interface to connect to an .mde file?

Sam

 

[thornmastr]

If making an mde file from an mdb file guaranteed a corruptionless environment, everyone would be using mde’s.

You can cause instant almost irreparable corruption to an mde or mdb file by attempting to open it with Word.

Any mdb or mde working on a networked configuration will almost always corrupt when there is a NIC failure.

Quoting from MS:
Saving your Access database as an MDE file prevents the following actions:
• Viewing, modifying, or creating forms, reports, or modules in Design view.
• Adding, deleting, or changing references to object libraries or databases.
• Changing code — an MDE file contains no source code.
• Importing or exporting forms, reports, or modules. However, tables, queries, data access pages, and macros can be imported from or exported to non-MDE databases.
Notice there is nothing said about corruption.

The ways to minimize the probability of corruption are:
Always split your database into front end back end.
Make sure your code is optimized to the best of your knowledge.
Use Access security to insure that users can do absolutely nothing to your tables other than read them via forms and queries. Give design permission on anything to no one but yourself.
Additionally, if you are setting up for a network:
Be sure all NIC’S on user PC’s are fully operational and a good quality brand, i.e. 3Com.
Make sure all queries request and act on the smallest recordset possible.

Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com

 

[thornmastr]

“Can you use a VB6.0 interface to connect to an .mde file?”

in most instances a vb6 connection is made to a back end database consisting of only tables. There is no reason to ever make a properly configured backend an mde file since mde’s are used to eliminate access to code and there cannot be code behind tables.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com

 

[Sam63]

I just have a severe corruption problem. The backend database corrupts about twice a month. I cannot figure out why? and most times I can't repair it, I have to have it restored from LAN backups.

Sam

 

[thornmastr]

Sam,

The first thing I would suggest is that you have your network department check the NICS in every user PC. One bad or failing card will give you consistent and predictable corruption.

You might want to check your code to insure you are not sending or receiving thousands of records when all you need are one or two. You really want to minimize the traffic flowing across the network.

Also, check where in the folder hierarchy of the networked drive the database resides. If it is lower than three folders deep, get your network administrator to move it up as close to the root folder of that drive as he possibly can.

Hopefully, some of these suggestions will help you.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com

 

[Rhonin]

Did you develop this database yourself or was it inherited?

I inherited one in the past that contained an inordinate number of tables with numerous validated fields.
One table had one field (validated with damaged info in the field).
Database would run fine for awhile... then down it would go.
Restore from backups... runs okay... for awhile, then down it would go.

It took some hunting to find the discrepant entry.
What I ended up doing was linking the tables to a new database, then using a query to poulate structure only copies of the existing tables. The query would append all entries but the problem ones. Took time but found the problem. Actually turned out to be more than one.

Anyway, once I went through the trouble of doing this, I have suffered only one crash in the last four months (server crash).

ps: .mde does not mean incorruptable. Wish it did...

Rhonin
&quot;too many questions, too little time...&quot;