Hiding Objects

[Guest]

How is it that when in one database I choose the option 'hide hidden objects' this applies itself to all databases I have created? I don't want to do this!

 

[Rick Brandt]

How is it that when in one database I choose the option 'hide hidden

objects' this applies itself to all databases I have created? I don't want
to do this!

Because it is an "Access" option, not an application option.

In Access 97 (I assume is similar in newer versions) you can go to the
"Advanced" tab while in Tools - Options and you will see a small squared
off section labeled "Current Database Only" Those three items are the only
ones in the entire options dialog that are file-specific. All of the other
options are for the installation of Access in general on that PC.

 

[Guest]

Thats a bit rubbish then isn't it? So if I then put this database in a shared location - things that I have hidden will not be hidden on someone elses PC if they haven't hidden objects as an option will they see them?

 

[Rick Brandt]

Thats a bit rubbish then isn't it? So if I then put this database in a

shared location - things that I have hidden will not be hidden on someone
elses PC if they haven't hidden objects as an option will they see them?

The ability to hide objects is not a security system. If you want that
then implement Access security. Easy obfuscation measures are not entirely
useless, but they assume a level of unsophistication on the part of the
users you are intending to hide things from.

You can hide the db window at startup. Many of your users would have no
idea how to display the window afterwards. Slightly more knowledgeable
users will.

You can disable the shift key and the F11 key. Now a higher level of user
will not know how to get it back. A still higher level of user will though.

You can hide your objects so they don't show in the db window. It will not
occur to many of your users to alter their option settings so these objects
are displayed. It might occur to some though.

You can name your objects prefixed with "USys" so they are treated as
system objects. Many users who might think about "show hidden objects"
won't think about "show system objects". Some might though.

The list goes on. Basically, the need to hide or secure stuff from
anything beyond a typical "clerical" user means you should utilize Access
User-Level security. While even this is hackable it raises the bar on how
skilled and/or motivated the hacker needs to be to the maximum you can
achieve with an Access application. Anything less than that is equivalent
to locking a screen door. That is not to say that there is no point in
locking a screen door (they all come with locks after all), but people who
do so understand what level of security that lock is getting them. As long
as you are aware of the limitations of the barriers you put in place and
still feel that they have merit, then there should be no problem.

 

[Dirk Goldgar]

The ability to hide objects is not a security system. If you want
that then implement Access security. Easy obfuscation measures are
not entirely useless, but they assume a level of unsophistication on
the part of the users you are intending to hide things from.

You can hide the db window at startup. Many of your users would have
no idea how to display the window afterwards. Slightly more
knowledgeable users will.

You can disable the shift key and the F11 key. Now a higher level of
user will not know how to get it back. A still higher level of user
will though.

You can hide your objects so they don't show in the db window. It
will not occur to many of your users to alter their option settings
so these objects are displayed. It might occur to some though.

You can name your objects prefixed with "USys" so they are treated as
system objects. Many users who might think about "show hidden
objects" won't think about "show system objects". Some might though.

The list goes on. Basically, the need to hide or secure stuff from
anything beyond a typical "clerical" user means you should utilize
Access User-Level security. While even this is hackable it raises
the bar on how skilled and/or motivated the hacker needs to be to the
maximum you can achieve with an Access application. Anything less
than that is equivalent to locking a screen door. That is not to say
that there is no point in locking a screen door (they all come with
locks after all), but people who do so understand what level of
security that lock is getting them. As long as you are aware of the
limitations of the barriers you put in place and still feel that they
have merit, then there should be no problem.

Very nicely put, Rick.

 

[Guest]

Point taken Rick. I think I need to try and suss out the Security element then. Thank you for your time and help. Sam