Using dbHiddenObject

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have an .mde file linked to a back table file.

If i set the attribute property for the tables in the back
table file as dbHiddenObject is there any side effect
problem that I must consider?

The idea is to reduce the possibility that a user access
the table file from a different front file by using the
current customized security file (.mdw).

Thanks
 
I have an .mde file linked to a back table file.

If i set the attribute property for the tables in the back
table file as dbHiddenObject is there any side effect
problem that I must consider?
Click to expand...

Yep! The tables for which you set that attribute will probably be *deleted*
on the next compact. dbhiddenobject is a system attribute, not a user one.
You should not be fooling with it!
The idea is to reduce the possibility that a user access
the table file from a different front file by using the
current customized security file (.mdw).
Click to expand...

Ensure that *all access* to the back-end tables, from your front-end file,
is through so-called "Run With Owner Permission" (RWOP) queries. Then, you
can set it up so that your users *can* use your front-end forms, reports
etc., but they *can not* access the back-end tables directly, or through any
other front-end file.

To do that, you need to set up user-level security. Unfortunately it is
fairly complex, with a steep learning curve, & many traps for the unwary.
Locate & read the Access Security FAQ for lots more information.

HTH,
TC
 
Back
Top