MDB keeps 'corrupting'

[Leslie Isaacs]

Hello All

I have an A97 backend mdb on a fileserver, with 4 PC's attached each with
its own frontend mdb. Everything has been working fine for years, but
recently I have been getting a message on one or other of the frontends that
the backend mdb isn't a database or needs repairing. I do the repair, and
all is OK ... for a few days, then the same thing happens again.

Any ideas?

I suppose I could create a new mdb, import all the tables from the existing
backend, then relink the frontends to the new backend. Not sure if that's
worth trying though.

Thnaks for any help.
Les

 

[ChrisM]

In message (e-mail address removed),

Hello All

I have an A97 backend mdb on a fileserver, with 4 PC's attached each
with its own frontend mdb. Everything has been working fine for
years, but recently I have been getting a message on one or other of
the frontends that the backend mdb isn't a database or needs
repairing. I do the repair, and all is OK ... for a few days, then
the same thing happens again.
Any ideas?

I suppose I could create a new mdb, import all the tables from the
existing backend, then relink the frontends to the new backend. Not
sure if that's worth trying though.

Thnaks for any help.
Les

First question has to be has ANYTHING changed on your network recently, even
somthing that would appear to have no bearing on the problem?
When you get the error about the corrupt database on one of the frontends,
do the rest continue to work or do the all then fail?

If nothing helpful to be gained from the above, it certainly can't do any
harm to do what you suggest, and import the tables into a new DB. It
shouldn't take long to do that. Make plenty of backups first though!!

 

[George Nicholson]

Just a guess: Any chance any of your users has "upgraded" their FE to a
later version of Access which is then "upgrading" the ac97 BE file? That
might account for the recurring "not a recognized database file" message to
the remaining 97 users.

Do you have any kind of audit trail built into your app? Any way to tell who
the last user was before the BE goes "bad"?

HTH,

 

[Leslie Isaacs]

Chris

Thanks for your reply.

Curiously, when one user gets the 'unrecognised database' message, one or
more of the other users can be unaffected - still working and connected to
the backend data. I cannot think of anything that has changed to cause this:
but in any case, even if something did cause it - once - I cannot understand
how, after doing a repair, all goes well for a few days then the problem
recurs. I cannot identify anything that happens just before the error.

I will try importing the tables into a new mdb.

Many thanks
Les

 

[Leslie Isaacs]

George

Thanks for your reply.

No-one will have attempted any upgrade on their FE - I know that.
Unfortunately I don't have any audit trail of users, so cannot use that.
Is it possible to say what kind of event could potentially be causing the
corruption (if that is what it is)? If I knew that I could at least ask the
users if they have been doing 'that event'. Otherwise I just can't think how
to get at the problem.
If you have any further ideas I would be very grateful

Thanks again.
Les.

 

[Tony Toews]

Curiously, when one user gets the 'unrecognised database' message, one or
more of the other users can be unaffected - still working and connected to
the backend data.

That's standard behavior. There is a flag set that tells someone
attempting to access the BE MDB that the MDB is corrupted. However
Access sessions already in the MDB aren't aware of that flag change.

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

 

[aaron.kempf]

MDB is ****ing crap don't use it for anything

seriously

Access Data Projects don't just 'crap out'

-Aaron