Unrecognized database format error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I was running Access 97 on a Windows ME system until my hard drive died.
Upgraded to XP on the new hard drive. Reloaded Access 97 and my database.
Now I get the above error message every time I try to open. Most of the
support pages that I've seen related to this error seem to focus on language
problems. I've never used anything other than U.S. English in setting up my
database on the old drive (ME). Haven't touched anything related to
languages on the new drive (XP).
 
1. While in Access but before you attempt to open the file - go to tools /
Database Utilities ...and do the compress & repair.

2. You now have xp...and so do you still have Access97? not sure I've ever
seen that combination - I wonder if that is part of the issue.

3. I would move the file onto a flash drive or via LAN move it to another
machine with Access97 or with any other version of Access and attempt the
open to see what happens...
 
2. You now have xp...and so do you still have Access97? not sure I've ever
seen that combination - I wonder if that is part of the issue.

Just FYI... Access97 (and for that matter Access 2.0) work fine on
WindowsXP.

John W. Vinson[MVP]
 
I put the file on a flash drive and moved it to a nearly identical system
with upgrade XP and Access 97. It worked just fine. Now totally confused.
Should I uninstall Access 97 on the original system and reload?????

KBAR
 
Sounds like a plan to me. And make sure you install all the service packs.
 
I just think that it's ridiculous to use A97 for anythiing.. it doesn't
support Access Data Projects!

I reccomend losing the training wheels and keeping current on your
version of Office

-Aaron
 
KBAR said:
I was running Access 97 on a Windows ME system until my hard drive died.
Upgraded to XP on the new hard drive. Reloaded Access 97 and my database.
Now I get the above error message every time I try to open.

What happens when you create a new database?
Most of the
support pages that I've seen related to this error seem to focus on language
problems. I've never used anything other than U.S. English in setting up my
database on the old drive (ME). Haven't touched anything related to
languages on the new drive (XP).

I wonder if the default workgroup file got somehow corrupted?

Tony

--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
do you seriously USE jet security?

worst feature ever made; other than Sharepoint FUnctionalist in 2003..
it's SLOW AS MOLASSES

JET security just sucks because you shouldn't need to manage security
in 3 different places NTFS permissions, SQL authentication AND jet?

Maybe you have time to deal with 3 different flavors of security.

I think that it's a waste of time and it's not strong enough to keep
out a simple dictionary attack... RIGHT?
 
With Access open, I tried to do a compress and repair to the DB. Got the
same error messsage. Then I removed and reloaded Access. Still have the
same problem. Then I created a new database. That worked just fine. Also,
I have no problems with the sample Northwind database. I still cannot open
my database even though a nearly identical machine (home) opens the database
up just fine.

Stumped and baffled,

KBAR
 
Kbar

Is there a difference in version numbers between the 2 machines? Maybe you
just need an update.
 
With Access open, I tried to do a compress and repair to the DB. Got the
same error messsage. Then I removed and reloaded Access. Still have the
same problem. Then I created a new database. That worked just fine. Also,
I have no problems with the sample Northwind database. I still cannot open
my database even though a nearly identical machine (home) opens the database
up just fine.

Have you tried creating a new, empty database and importing everything
from the corrupt one?

John W. Vinson[MVP]
 
I reccomend using a real database format.

entrusting your DATA to a file that contains a VBA project?


ROFL

what an awful ass design
 
Yep. I created the new database, then tried to import. Got the same error
message as soon as I tried to import.
 
sorry I dont know who told you to ever use MDB for anything; but they
were wrong.

MDB is unreliable and unpredictable

-Aaron
 
Just learned something interesting..... The machine in my office (where
Access is not working) is version Access 97 version 8. The home computer
(where Access is working) is version 9. Is this my problem and how do I
resolve?

Thanks,

KBAR
 
Just learned something interesting..... The machine in my office (where
Access is not working) is version Access 97 version 8. The home computer
(where Access is working) is version 9. Is this my problem and how do I
resolve?

It almost certainly is! Access over the years has been pretty finicky
about version consistancy. Either version 8 OR version 9 would
probably work fine; but creating a database in one version and running
it in a different version is asking for trouble.

Try deleting the form on the office computer, *compacting the
database* to remove any residue of it, and recreating the form from
scratch, there. Avoid modifying it on the other computer, if it *does*
work - that might break it again!

John W. Vinson[MVP]
 
Access 9 or 2000 will open version 97 or 8 but Access 97 will not open
version 9 (Access 2000). To resolve either get a license for Access 2000
(not sure if you can still buy) or Access 2003 (which will open 97, 2000 and
XP) for both machines.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top