Unrecognized db format

[Ra]

Hello everyone,

I had this multi-user application installed on the common drive since May.
It's Access 2003, and two days ago started getting the "unrecognized db
format" mesage. I tried importing all into a blank db, got the same message
and no import. The issue was reported by multiple users.
Please let me know what you think.

Thank you,
Ra

 

[Daniel Pineault]

How was your db setup. You mention multiple users... so your db was split so
the each user had their own front-end? What type of maintenance did you
implement?Do you have a backup?!

Have you compacted the db recently. Sadly, I'm thinking database corruption
possibly!

Take a look at http://www.granite.ab.ca/access/corruptmdbs.htm

 

[Ra]

It is a non-split multiuser set up, auto compact on close. I do have a back
up, am in process to get it. Trying to figure out what went wrong.

 

[Arvin Meyer [MVP]]

The first thing that is wrong is that the database is not split. Your
database is probably corrupt. You MUST split a database to use it in a
multi-user environment. The backend goes on a server and a copy of the
front-end goes on each workstation. If you have a backup, split it before
you put it back in service. If not, here are some of the things you can try:

First, always work on a copy of the database. Working on the original may
make it impossible for a repair service to fix it.

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

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

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com

 

[Dale Fye]

I would also turn off the Compact on Close (for both the front end and the
backend), once you have split the application. I've found that this can be
the cause of corruption. If your front-end is designed correctly, you should
almost never need to compact it anyway. If you use temporary tables in your
front end, then these should be created in a temp table mdb file (I call mine
app_TempFiles.mdb, where I replace 'app' with the name of my app). Then you
add all of your temp tables to this, give the users each a copy of this temp
table in addition to their copy of the front end, and link each users front
end to their individual temp table.

HTH
Dale
--
Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

 

[Ra]

I restored the application with a Friday b-up. In process of splitting and
installing fe on all users machines.
I read about this "compact on close" before, what is the reason behind
disabling it?

 

[pam]

I restored the application with a Friday b-up. In process of splitting and
installing fe on all users machines.
I read about this "compact on close" before, what is the reason behind
disabling it?

It's cool

 

[Tony Toews [MVP]]

I restored the application with a Friday b-up. In process of splitting and
installing fe on all users machines.
I read about this "compact on close" before, what is the reason behind
disabling it?

Can cause lots more trouble than it solves. Also doesn't make sense
to use it in a FE/BE environment as Access never opens the BE in the
GUI explicitly. So you only compact on close the FE. Which seldom if
ever needs compacting.

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
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[David W. Fenton]

Can cause lots more trouble than it solves.

The reason for that is that some kinds of corruption leave an MDB
readable and the data accessible, but when compacted, the data is
lost forever. Thus, if you have corruption and you COMPACT ON CLOSE,
you may lose data that would otherwise have been recoverable had you
not compacted.

 

[guiatin]

salut les amis bonne fête de fin d'année

"David W. Fenton" <[email protected]> a écrit dans le message de
groupe de discussion :
[email protected]...