Corrupt MDE

[Robinson]

I am always able to recreate the MDE from the MDB, but the
MDE appears to be corrupt quite a bit. Users report that
they are exiting Access properly.

Please advise

 

[GVaught]

It is unwise to share an mde that contains the master tables, queries, forms
etc. Your mdb should be split into two databases. One will contain only your
master tables and should remain as an mdb and placed on a machine that is
classified as a server and not an workstation. The users will get the second
database, which will contain linked tables, queries, forms, reports and
resides on their own machines. This database can be converted to an mde. The
one consideration you must provide is a way for them to link their tables to
the master database on the server. You can create the link within the mdb
that reflects the link that all users will use such as, a mapped drive
letter of E:\.... to the server. The other way is create code that will
automatically prompt the user to locate the backend via a dialog box.

 

[Nikos Yannacopoulos]

I agree with GVaught, just want to stress the importance of each user having
their own copy of the front end .mde on their local HDD (as opposed to a
common FE on the server, which leads to corruptions).

You might also want to take a look at Tony Toews' auto FE updater:

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

which will refresh the FE on users' PC's every time a new version of it is
found on the server.

HTH,
Nikos

 

[robinson]

Thank you very much. I inherited a process where both the
mdb and the mde reside on a server. The user in question
has windows 2000 and office xp. I am going to upgrade the
jet engine. My concern is that it has happened quite a
bit (almost once a week) in the last month. I will also
look deeply into putting the Mde on the workstation. If
there is anything else I should try let me know. I got rid
of a lot of bloat, compact and repaired the mdb. Once
again thanks for your help.

 

[Nikos Yannacopoulos]

I think the most important part is the local .mde. A common .mdb is known to
lead to frequent corruptions, like you had. If it were a Jet incompatibility
problem it would manifest itself right from the beginning, not occasionally.

Nikos