secured of database

M

Michael Lam

Dear all

Do the following way a good practise to protect a database

Change the file to MDE file

Enable the following option of
default form for opening but disable all other menu buttons

keep the original secured

(if any amendment to the program is required , just use export function
of table to the original database with both definition and sources selected)
Do the amendment and create MDE file again


Michael Lam
System Administrator
 
T

TC

(snip)
(if any amendment to the program is required , just use export function
of table to the original database with both definition and sources selected)
Do the amendment and create MDE file again


It is not a good idea to have everything in a single database file. This
makes it difficult to distribute program changes. Instead, use a "front
end/back end" structure. The back end (BE) database has all of the tables,
but nothing else. The front end (FE) database has all of the queries, forms,
reports, macros & modules. The FE links to the actual tables in the BE.

Then, when you want to distributre program changes, you just send a new copy
of the whole FE database. The users copy that new version, over their new
version. You do not need to export then re-import the data.

Hope this helps,
TC
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top