How do I protect my Access database design?

[Janice B]

I've designed a database for my colleagues to use to log work given to our
Admin section. How can I ensure they are not able to alter the design?

Basically, all they need to be able to do is fill in a form that has been
created, although the Admin staff may wish to create queries now and again.
Can I password control the design element?

 

[Daniel]

You could either implement user-level security and lock down which users can
alter the design or simply distribute your db as an mde to the users and you
are the only one with the mdb (which can be altered).

 

[Janice B]

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?

Thanks for your help.

 

[Scott McDaniel]

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.

 

[Amy Blankenship]

I've designed a database for my colleagues to use to log work given to our
Admin section. How can I ensure they are not able to alter the design?

Basically, all they need to be able to do is fill in a form that has been
created, although the Admin staff may wish to create queries now and
again.
Can I password control the design element?

If they're not terribly sophisticated, you can simply hide everything you
don't want them seeing. If they're slightly sophisticated, you can split
the database and only give them the front end. The front end won't have any
tables in it, and if the database with the tables in it is somewhere off in
the ether they won't see it unless they go looking for it. They will still
be able to add queries to their own copy of the front end.

HTH;

Amy

 

[Maurice]

Janice,

Goto - Tools - database utilities - create MDE file (somewhere at the bottom
of the menu-items). You'll be prompted for a location and by default it will
create an MDE with the same filename as the MDB. Be very carefull with the
mdb because an MDE can't be undone!. If you have to alter anything you do
that in de MDB and create a new MDE from that one again.

If is is a split- database it will still redirect to the backend from the
mdb. If it's a stand alone version it will feedback to the MDB. So splitting
your MDB might be your
best choice here..

hth

 

[Janice B]

Thank you.

Now, hopefully this is my last question. For some reason my database has
saved as in Access 2000 file format even though I'm using Access 2003. This
means I can't use the MDE file option - how can I change the file format from
2000 to 2003?

Thanks again - first time I've asked a question on here and you are all very
helpful.

 

[Janice B]

I think the first method would be secure enough. So how do I save the
database as an mde file? We have a network drive so I can place it on there
to make sure everyone accesses it. If I have the .mdb file in a different
folder will the .mde file still feed back to it?

Sorry to ask so many questions, I've not used Access for ages and
volunteered to design this without thinking about the complicated parts!

 

[Amy Blankenship]

I think the first method would be secure enough. So how do I save the
database as an mde file? We have a network drive so I can place it on
there
to make sure everyone accesses it. If I have the .mdb file in a different
folder will the .mde file still feed back to it?

Sorry to ask so many questions, I've not used Access for ages and
volunteered to design this without thinking about the complicated parts!

You really should split the database if this is what you want to do.

-Amy

 

[Joan Wild]

Tools, Database Utilities, Convert Database...

After converting, open the 2003 version, hit Ctrl-G and Debug, Compile. Close that window and Tools, Database Utilities, Compact.

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

If you go into Tools, Options, you can set it so that Access always creates a 2002/2003 format, rather than the default 2000.

 

[jen85]

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?