How do I protect my Access database design?

I have read this response and it has helped with my problem. However, I
wonder if i were to change my database to .mde, and the users would continue
to access the .mde file and update data, does the updated data then get
transferred to the .mdb so that if i do have any changes eventually to make
to the .mdb, the data is updated and current?
Or is this .mde more like a mode to transfer to when completely done
altering design?

"Scott McDaniel" wrote:

On Thu, 24 May 2007 06:39:01 -0700, Janice B wrote:

That sounds like what I want to do Daniel. Can I be a total pain and ask how
I do it? I think letting the workers have it as an mde may work......would
that feed back to the original db so that any forms filled by them would show
up collectively?

An mde file operates exactly like an .mdb file, except users cannot enter design view of any form/report/module. Users
can still access the tables and queries, however, assuming they have the knowledge to do so (users can simply link to
your .mde file from another Access db to do this). If your app opens any form/report in design view, you won't be able
to use the mde format.

If you want to remove access to the Tables and Queries, then as Daniel suggested you'd need to move to ULS, secure the
database, then add RWOP (Run With Owner Permission) queries for all data access, then remove all access to the tables.
It's a LOAD of work, to be sure, but it's the best method available at this time.