cdgaefke 0 Newbie Poster

In Access 97, the repair and compact methods are separate. In Access 2003, they appear to be the same. That goes along with everything I've seen ... the JetComp utility does it all in one, and the JRO method does as well.

I assume this didn't fix your problem?

If not, other things I'd check are:

- Try to have the version of the database match the version of Access, if possible. That is, if you have Access 2003, don't use it on an Access 97 or Access 2000 database.
- Check your connection method. How are you establishing the connection to the Access database? The most direct, efficient, and safe is with Jet 4. If you aren't sure, can you post the connection string used on the connection object? (Might be an ADO control or an actual ADODB.Connection object, or something else still.)

I'm going under Tools/Database Utilities/Compare and Compact Database, but it keeps giving me the change to open a database over and over, but never to repair it. I'm using Access 2003. What am I missing?

cdgaefke 0 Newbie Poster

Hi, from my experience, this usually happens when the Access database is corrupt, or in the process of going corrupt. Try using the Access repair utility and see if it corrects your error.

Charles

I've got a VB app I wrote that runs over Access and works pretty well for the most part. However, there are a couple of pages where I get the following error when trying to access a database (no pun intended).

I'm getting the error "Unrecognized Database Format (path to .mdb file)". This seems to happen both if I'm trying to load a grid or a data control. The program keeps running after I hit "OK", but no data is loading into the objects (of course).

Any ideas?