Hi,
how can I set an access object unvisible with VBA?
I habe access 2000

Thanks
TNL
..

me.objectname.visible = False
or
Forms!myform!objectname.visible = False
--
Alex Dybenko (MVP)
http://Alex.Dybenko.com



"TNL" <(E-Mail Removed)> wrote in message
news:0a9701c3581c$f0aa3140$(E-Mail Removed)...
> Hi,
> how can I set an access object unvisible with VBA?
> I habe access 2000
>
> Thanks
> TNL
> .
>
>

Hi,
I don't think a control on a Form, but an object such as a
query, a table on the database window.
on the dialog property we can make them unvisible, but
with VBA?

TNL

>-----Original Message-----
>me.objectname.visible = False
>or
>Forms!myform!objectname.visible = False
>--
>Alex Dybenko (MVP)
>http://Alex.Dybenko.com
>
>
>
>"TNL" <(E-Mail Removed)> wrote in message
>news:0a9701c3581c$f0aa3140$(E-Mail Removed)...
>> Hi,
>> how can I set an access object unvisible with VBA?
>> I habe access 2000
>>
>> Thanks
>> TNL
>> .
>>
>>
>
>
>.
>

"Roger" <(E-Mail Removed)> wrote in message
news:00c001c3583e$7dc0f480$(E-Mail Removed)...

> To hide a table definition in VBA you can use:
> CurrentDB.TableDefs("TableName").Properties("Attributes")
> =dbHiddenObject

All such tables will be *deleted* on the next compact!

This is possibly not what he wants.

dbHiddenObject is an undocumented system property.

It is *not* for what its name implies.

TC

"TC" <(E-Mail Removed)> wrote in news:1059799801.502673@teuthos:

>
> dbHiddenObject is an undocumented system property.
>
> It is *not* for what its name implies.
>
>

It is documented... but I agree it's really stupid. There was a similar
thread hereabouts a week or two ago, where we decided that

Application.SetHiddenAttribute

was the way to go.

All the best


Tim F