Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

"Unrecognized database format"

0 views
Skip to first unread message

Susan

unread,
Sep 25, 2003, 1:38:31 AM9/25/03
to
I have been using Office 2000 Professional. I have a
database that has been working great until yesterday. Now
when I went to open it I get message" Unrecognized
database format". How do I fix this? Is my info still
there somewhere? I don't even know where to begin.
Thanks, Susan

Van T. Dinh

unread,
Sep 25, 2003, 2:26:42 AM9/25/03
to
You database is corrupted. See Tony Toews' article:

<http://www.granite.ab.ca/access/corruptmdbs.htm>

HTH
Van T. Dinh
MVP (Access)

>.
>

Al Moroz

unread,
Sep 25, 2003, 2:33:21 AM9/25/03
to
It may be corrupted. Make a backup of the database first
then open Access, select <Tools | Database Utilities |
Compact and Repair Database...>. It'll ask you which
database to Compact and Repair, then ask you what to name
the new database.

Al Moroz
http://www.abacus-strategies.com

**NOTE: Do not respond to the email address, it's for
Newsgroups only

>.
>

Rich

unread,
Sep 25, 2003, 4:56:14 AM9/25/03
to
Came accross a similar situation with a PC that was
running both Access97 and Access2K. It seems the last
version to run takes over the association with the .mdb
file extension when launching from a shortcut or windows
explorer.

My resolution was:

Open the file from Access2K directly not from a shortcut.
That is: open Access2K first, then do the File | Open
method to launch the database.

Hope this helps. Rich

>.
>

Susan

unread,
Sep 25, 2003, 12:02:25 PM9/25/03
to
When I try to do the compact and repair it simply displays
the same error message "unrecognized database format".
Anything else I should try? Susan

>.
>

Susan

unread,
Sep 25, 2003, 12:06:05 PM9/25/03
to
I did give that a try and it displays the same message
when I try to "compact and repair". Thanks for trying
however......... Susan
>.
>

Gina Whipp

unread,
Sep 25, 2003, 12:25:59 PM9/25/03
to
Happened to me once, here's what I did... Create a new database and
importing the all the objects except the forms to the new one. Test all the
queries, mods, macros, etc... by opening them, if all appears fine then it's
a form and this could take some time. Import one form at a time till you
find the bad then recreate. But this will take some time but better then
recreating the entire database from scratch 8-)

Doesn't always work as sometimes you can't import the objects in. Maybe
someone else will have a better idea.


"Susan" <splu...@msn.com> wrote in message
news:01ec01c3837e$6985cc00$a301...@phx.gbl...

Van T. Dinh

unread,
Sep 25, 2003, 6:29:39 PM9/25/03
to
I am sure Tony Toews' article advises a lot more methods than just Compact &
Repair. For example: using JetComp.exe and also import everything into a
new database as per Gina's advice.

--


HTH
Van T. Dinh
MVP (Access)

"Susan" <splu...@msn.com> wrote in message
news:01ec01c3837e$6985cc00$a301...@phx.gbl...

0 new messages