How to protect my database

28 Nov 2007 2:34 AM

hrbsh97

I have a personnel database that I have developed .. I would like to share
this database for others to use for information lookup in Access and for use
in Word documents (merges & such) .. I am planning on putting this database
out on our server on a shared folder. I don't mind who uses it .. however,
here is the biggie .. I would like to restrict it so that users can view &
use in Word but not change my design or add/delete information. What is the
simplest/best way to do this? ..

I would appreciate any help you could all give me :) .. thanks!

28 Nov 2007 8:33 AM

Keith Wilby

Show quote

"hrbsh97" <hrbs***@discussions.microsoft.com> wrote in message
news:5D2640C1-3E12-49F3-A0EC-E54C107E295B@microsoft.com...
>I have a personnel database that I have developed .. I would like to share
> this database for others to use for information lookup in Access and for
> use
> in Word documents (merges & such) .. I am planning on putting this
> database
> out on our server on a shared folder. I don't mind who uses it ..
> however,
> here is the biggie .. I would like to restrict it so that users can view &
> use in Word but not change my design or add/delete information. What is
> the
> simplest/best way to do this? ..
>
> I would appreciate any help you could all give me :) .. thanks!

I would say the simplest way is to split the database and supply each user
with an mde front end with the bypass key disabled, all startup options
disabled, and provide custom menus.

Protect your back end the same way and by putting it on a hidden share with
delete file permissions removed.

HTH - Keith.
www.keithwilby.com

29 Nov 2007 4:03 AM

hrbsh97

Thanks for the reply :) ..

You mentioned the following:

mde front end with the bypass key disabled, all startup options disabled,
and provide custom menus. You also said to protect your back end the same
way and by putting it on a hidden share with delete file permissions removed.

Can you give me more information on how to do this? .. or point me in the
right direction to find out how to do this? ..

Many thanks!!!

Show quote

"Keith Wilby" wrote:

> "hrbsh97" <hrbs***@discussions.microsoft.com> wrote in message
> news:5D2640C1-3E12-49F3-A0EC-E54C107E295B@microsoft.com...
> >I have a personnel database that I have developed .. I would like to share
> > this database for others to use for information lookup in Access and for
> > use
> > in Word documents (merges & such) .. I am planning on putting this
> > database
> > out on our server on a shared folder. I don't mind who uses it ..
> > however,
> > here is the biggie .. I would like to restrict it so that users can view &
> > use in Word but not change my design or add/delete information. What is
> > the
> > simplest/best way to do this? ..
> >
> > I would appreciate any help you could all give me :) .. thanks!
>
> I would say the simplest way is to split the database and supply each user
> with an mde front end with the bypass key disabled, all startup options
> disabled, and provide custom menus.
>
> Protect your back end the same way and by putting it on a hidden share with
> delete file permissions removed.
>
> HTH - Keith.
> www.keithwilby.com
>
>

29 Nov 2007 8:38 AM

Keith Wilby

"hrbsh97" <hrbs***@discussions.microsoft.com> wrote in message
news:92DD3018-F8D1-487C-9503-1A90A81929C4@microsoft.com...
> Thanks for the reply :) ..
>
> You mentioned the following:
>
> mde front end

Create an mde file using the Tools, Database Utilities menu item.

> with the bypass key disabled,

http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

> all startup options disabled,

Uncheck all options under Tools, Startup.

> and provide custom menus.

You need to create your own menus because you are removing the option to
show built-in menus at startup so that users can't access your db window.

> You also said to protect your back end the same
> way and by putting it on a hidden share with delete file permissions
> removed.

You need server admin rights to do this but you map a network folder, share
it (it will have a "$" suffix) and hide it. Use folder permissions to
remove evberyone's (except yours) ability to delete the BE.

If none of this means anything to you then please practice on dummy files,
you could very easily screw up.

HTH - Keith.