Distribution of MDE Database

[Jk]

Hello,

I completed my database and need to release it to a few
users through a shared folder(back end in folder and front
end copied to desktops then link to shared folder)I would
like to convert my database to MDE to prevent changes to
design.Does coverting the file present problems in the
distribution i have described above?

Thank you

 

[Joan Wild]

Hello,

I completed my database and need to release it to a few
users through a shared folder(back end in folder and front
end copied to desktops then link to shared folder)I would
like to convert my database to MDE to prevent changes to
design.Does coverting the file present problems in the
distribution i have described above?

Making a MDE will prevent changes to forms, reports, and modules; not
queries or macros. It is still a good idea though. There is little point
in making the backend a MDE since it doesn't affect tables.

Be sure to keep a copy of the MDB in case you need to make design changes.

 

[Guest]

Hello,

Thanks for the quick response.So i would keep a copy of
the mdb file?Would that be something like storing a copy
on a separate drive?Could you detail how would i go about
making changes once the file is in MDE format?

 

[Joan Wild]

Hello,

Thanks for the quick response.So i would keep a copy of
the mdb file?Would that be something like storing a copy
on a separate drive?Could you detail how would i go about
making changes once the file is in MDE format?

I would keep the mdb in a safe place, yes. If you need to make any design
changes to any objects, or add new ones, do so in the MDB version. Once you
are finished with the changes and want to distribute, you again make a mde
and send that.

You can automate the updating of the frontend to users. Have a look at Tony
Toews site for a utility - frontend updater.
http://www.granite.ab.ca/access/autofe.htm
[/QUOTE]