Where is Table 'Hidden' Property?

[aybs10]

Hi there - I can't seem to locate the 'hidden' property for a table. I'd
like to be able to manipulate this from code. Anybody know how?

thanks

 

[Tim Ferguson]

Hi there - I can't seem to locate the 'hidden' property for a table. I'd
like to be able to manipulate this from code. Anybody know how?

I was looking at this in response to another post recently. There are two
different ways to hide a table:

1) you can select it in the database window and open its properties window
and check "Hidden" -- it will be visible only if you select Tools | Options
| View | Hidden Objects.

2) you can use code to set the Attributes property of the appropriate
TableDef object:

db.TableDefs("Temp").Attributes = _
db.TableDefs("Temp").Attributes Xor dbHiddenObject

but in this case the table stays disappeared even when Hidden Objects are
turned on in Tools | Options.

To date, I have not found any crossover between the two methods, unlike in
Excel where there is xlVisible and xlVeryHidden, but also has xlHidden in
between.

HTH


Tim F

 

[Paul Overway]

Note that tables hidden using your second method will be deleted when
database is compacted....so, not a good idea to use this method.

 

[david epsom dot com dot au]

The only supported method is to use table names starting 'Usys' (User System
tables) Visible when system tables are visible: invisible when system tables
are not visible.

(david)

 

[Tim Ferguson]

Note that tables hidden using your second method will be deleted when
database is compacted....so, not a good idea to use this method.

Not that I have ever _used_ this method so I would not have known this. But
this seems like an incredibly stupid bug...

Tim F

 

[david epsom dot com dot au]

this seems like an incredibly stupid bug...

I prefer to think of it as a documentation bug, but
even MS employees have been caught here. The property
should have been called something like 'deleted' or
'temporary', but since it is called 'hidden', and has
the effect of hiding the table from the Access IDE,
people continue to discover and misuse it.....

I think the real problem is the failure to expose the
Access 'hidden' property to the Access Automation
interface -- if that was available, people wouldn't
go looking at the DAO interface at all.

(david)

 

[Dirk Goldgar]

I prefer to think of it as a documentation bug, but
even MS employees have been caught here. The property
should have been called something like 'deleted' or
'temporary', but since it is called 'hidden', and has
the effect of hiding the table from the Access IDE,
people continue to discover and misuse it.....

I think the real problem is the failure to expose the
Access 'hidden' property to the Access Automation
interface -- if that was available, people wouldn't
go looking at the DAO interface at all.

Don't the Application.GetHiddenAttribute and .SetHiddenAttribute methods
(in A2K+) do this?

 

[Tim Ferguson]

Don't the Application.GetHiddenAttribute and .SetHiddenAttribute methods
(in A2K+) do this?

Well, well: I never heard of that before!

In the meantime, I'll revise my original comment: "But
this seems like an incredibly stupid bug^W property name..."

All the best


Tim F

 

[david epsom dot com dot au]

....That's my punishment for using the A97 help file...

(david)