dbHiddenObject table attribute

[Vic Spainhower]

Hello,

I am using the dbHiddenObject attribute to hide a table in Access 2002 and
it seems to work fine. I have read here in the newsgroup that after a
compact operation the hidden tables are deleted. However, I am not seeing
this problem. I tried the same thing in Access 97 and the table does get
deleted.

Can anyone confirm this problem to be fixed in Access 2002. The MS Knowledge
base article shows the attribute for temporary use but it states Access 2000
with no mention of Access 2002. What I Like about this method is it will not
show unless you know the exact name of the table and knowledge of the
attribute. But before I head down this path I would like some assurance that
it won't be problematic!


Thanks Very Much!


Vic

 

[Van T. Dinh]

It was a Bug, not "by design" Property so it may have been fixed in AXP.
Normally in this case, Microsoft does not mention the bug in new Access
version.

Also, since you know the Bug, it should be easy to fix if the bug affects
your AXP database. You can simply do a few tests with dummy Tables and see
if the bug does occur in AXP.

 

[Dirk Goldgar]

Hello,

I am using the dbHiddenObject attribute to hide a table in Access
2002 and it seems to work fine. I have read here in the newsgroup
that after a compact operation the hidden tables are deleted.
However, I am not seeing this problem. I tried the same thing in
Access 97 and the table does get deleted.

Can anyone confirm this problem to be fixed in Access 2002. The MS
Knowledge base article shows the attribute for temporary use but it
states Access 2000 with no mention of Access 2002. What I Like about
this method is it will not show unless you know the exact name of the
table and knowledge of the attribute. But before I head down this
path I would like some assurance that it won't be problematic!

If you want to spare yourself this worry, you can use the
Application.SetHiddenAttribute to hide or unhide various database
objects. That's not available in Access 97, but it's safe in Access
2000 and 2002.

 

[Vic Spainhower]

Dirk,

The problem with the Application.SetHiddenAttribute is all the user has to
do is turn on Hidden Objects and there it is. What I'm doing is adding a
User Login table which will contain features they have purchased. If they
were able to see the table they would be able to use particular features by
simply signing on as a different user that would have the feature available.

Vic

 

[Dirk Goldgar]

Dirk,

The problem with the Application.SetHiddenAttribute is all the user
has to do is turn on Hidden Objects and there it is. What I'm doing
is adding a User Login table which will contain features they have
purchased. If they were able to see the table they would be able to
use particular features by simply signing on as a different user that
would have the feature available.

You know, I had to go check that, because I hadn't realized that setting
the dbHiddenObject attribute would keep the table hidden even if View
Hidden Objects was set. But you're right, it does. Nevertheless, I'm
always suspicious of any security scheme that relies on ignorance of the
scheme's existence. I'd be more likely to institute user-level (i.e.,
workgroup) security, and revoke the users' permissions on that table.