MDE question

[Mary]

In previous posts, everyone agrees it's best to give each user their own copy
of the MDE file. I'll probably have to update the MDE file periodically, is
there an easy way to distribute updates, or would users have to overwrite
their existing copy.

What are the drawbacks of having one MDE file on a shared server with 10
users?

New to MDE's, thanks for your advice.

Mary

 

[Rick B]

I would automate the update process. If you do some searches on previous
posts, you should find lots of suggestions.

Go to google.com and click the "groups" button. Then enter the following
search string...



microsoft.public.access update front-end

 

[TC]

Hopping in here (because I can not see the original post).

Mary, just in case you don't know this, the need to split a database
into a front-end/back-end structure, is nothing to do with it being (or
not being) an MDE. The need is identical in either case. It arises when
the database will be used simultaneously by several people. It is
commonly believed that an un-split database is prone to corruption in
that circumstance. AFAIK, that is nothing to do with whether the db is
or isn't an MDE.

HTH,
TC