Security

5 Sep 2007 5:12 PM

sandrao

I would just like a simple way of preventing someone from going to the tables
or others items in the background. I have created a scheduling database.Some
of the users with some access knowledge messing with the programs and
altering the original design. How can I simply stop them from getting access
to the backgroud without creating a complicated security system. Is there a
way to lock access files alowing the use of the data entry forms. Also when
needed how can I easily get access to make other modifications if necessary.
I know about the Hidden obects provision but I think they do also. Any
suggestions

sandrao

5 Sep 2007 7:16 PM

Joan Wild

There are a number of things you can do:

Backup your database; you can easily lock yourself out playing around with these features.

Create custom menus/toolbars for use throughout your application.
Create a startup form (a main menu form if you have one) that is opened on startup.
Use the features in Tools, Startup to
        set the startup form
        set your default menu (the custom one you made)
        disable all the checkboxes about allowing built in menus, toolbars, changes etc.
        hide the db window (ensure the custom menu you create does not include the Windows, Unhide item)
        Uncheck the allow special keys (this will disable the F11 key, among others)

If you need to bypass these startup features, you can hold the shift key down while you open the db. If you feel that your users may use this to bypass your settings, you can disable the shift key bypass - there's an example in help for doing this(look for AllowBypassKey) or at
http://www.mvps.org/access/modules/mdl0011.htm
and
http://www.mvps.org/access/general/gen0040.htm

You can also create a MDE from your database, which will prevent changes to forms, reports and modules (If you do this, be certain to keep your original mdb in case you need to make changes).

Beyond doing this, you can implement user level security (and still do the above). However if your users are determined, they can search and find security crackers on the internet.

--
Joan Wild
Microsoft Access MVP

Show quote

"sandrao" <sand***@discussions.microsoft.com> wrote in message news:398A8B1F-E19D-47FF-9CBD-786A2083C1A4@microsoft.com...
>I would just like a simple way of preventing someone from going to the tables
> or others items in the background. I have created a scheduling database.Some
> of the users with some access knowledge messing with the programs and
> altering the original design. How can I simply stop them from getting access
> to the backgroud without creating a complicated security system. Is there a
> way to lock access files alowing the use of the data entry forms. Also when
> needed how can I easily get access to make other modifications if necessary.
> I know about the Hidden obects provision but I think they do also. Any
> suggestions
>
> sandrao

5 Sep 2007 8:06 PM

sandrao

Thanks. Will look at the suggestions. But as you said if they are
determined there not much one can do.

Show quote

"Joan Wild" wrote:

> There are a number of things you can do:
>
> Backup your database; you can easily lock yourself out playing around with these features.
>
> Create custom menus/toolbars for use throughout your application.
> Create a startup form (a main menu form if you have one) that is opened on startup.
> Use the features in Tools, Startup to
>         set the startup form
>         set your default menu (the custom one you made)
>         disable all the checkboxes about allowing built in menus, toolbars, changes etc.
>         hide the db window (ensure the custom menu you create does not include the Windows, Unhide item)
>         Uncheck the allow special keys (this will disable the F11 key, among others)
>
> If you need to bypass these startup features, you can hold the shift key down while you open the db. If you feel that your users may use this to bypass your settings, you can disable the shift key bypass - there's an example in help for doing this(look for AllowBypassKey) or at
> http://www.mvps.org/access/modules/mdl0011.htm
> and
> http://www.mvps.org/access/general/gen0040.htm
>
> You can also create a MDE from your database, which will prevent changes to forms, reports and modules (If you do this, be certain to keep your original mdb in case you need to make changes).
>
> Beyond doing this, you can implement user level security (and still do the above). However if your users are determined, they can search and find security crackers on the internet.
>
> --
> Joan Wild
> Microsoft Access MVP
> "sandrao" <sand***@discussions.microsoft.com> wrote in message news:398A8B1F-E19D-47FF-9CBD-786A2083C1A4@microsoft.com...
> >I would just like a simple way of preventing someone from going to the tables
> > or others items in the background. I have created a scheduling database.Some
> > of the users with some access knowledge messing with the programs and
> > altering the original design. How can I simply stop them from getting access
> > to the backgroud without creating a complicated security system. Is there a
> > way to lock access files alowing the use of the data entry forms. Also when
> > needed how can I easily get access to make other modifications if necessary.
> > I know about the Hidden obects provision but I think they do also. Any
> > suggestions
> >
> > sandrao
>