Security FAQ > TableDef (?)

  • Thread starter Thread starter tbl
  • Start date Start date
T

tbl

In the Security FAQ, Section 14, it mentions that you "need
to have Read Data permissions on the TableDef object in the
source database" to refresh existing table attachments.

What is the "TableDef" object, and how do I set the
permissions for it?

By "source database", is the author referring to the
back-end tables?
 
In the Security FAQ, Section 14, it mentions that you "need
to have Read Data permissions on the TableDef object in the
source database" to refresh existing table attachments.

What is the "TableDef" object, and how do I set the
permissions for it?
Click to expand...

A "TableDef" is just a table; the DAO object for a table is known as a TableDef, and if needed, you would
programatically manipulate permissions on the "TableDef" object.
By "source database", is the author referring to the
back-end tables?
Click to expand...

Yes. You'd set those perms in the backend (make sure to use the same workgroup file to secure both the backend and
frontend).

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
A "TableDef" is just a table; the DAO object for a table is known as a TableDef, and if needed, you would
programatically manipulate permissions on the "TableDef" object.


Yes. You'd set those perms in the backend (make sure to use the same
workgroup file to secure both the backend and
frontend).
Click to expand...


Thanks Scott.

I've been trying to understand why our satellite office
can't use the Linked Table Manager when they try to put the
back-end on the LAN and the front end on a couple of
workstations.

This is an Access 2000 mdb used on Access 2002 machines,
under Win2k.

After reading thru the FAQ, it seemed like the "Field
Admins" group should be able to use the linked table
manager, but the FAQ is not very clear on this (to my little
brain). But maybe the FAQ is saying that to have the tables
secured, and *still* allow limited users to use the Linked
Table Manager, coding is needed. I'm not a coder, so the
coding offered would have to be good-to-go as is, or I'd be
sunk.

I've gone so far as to give the "Field Admins" open/run
permissions on the back-end db, and all permissions except
Administer on the tables, queries, forms, reports, and
macros, but still they can't use the LTM, and I don't know
why. Access knows, but it won't tell me! ;-l

Thanks again for your reply.
 
Thanks Scott.

I've been trying to understand why our satellite office
can't use the Linked Table Manager when they try to put the
back-end on the LAN and the front end on a couple of
workstations.

This is an Access 2000 mdb used on Access 2002 machines,
under Win2k.

After reading thru the FAQ, it seemed like the "Field
Admins" group should be able to use the linked table
manager, but the FAQ is not very clear on this (to my little
brain). But maybe the FAQ is saying that to have the tables
secured, and *still* allow limited users to use the Linked
Table Manager, coding is needed. I'm not a coder, so the
coding offered would have to be good-to-go as is, or I'd be
sunk.

I've gone so far as to give the "Field Admins" open/run
permissions on the back-end db, and all permissions except
Administer on the tables, queries, forms, reports, and
macros, but still they can't use the LTM, and I don't know
why. Access knows, but it won't tell me! ;-l
Click to expand...

Have you given the group the same permissions for NEW tabledefs (i.e the <Net Tables/Queries> selection on the Object
Name listing, in the User and Group Permissions dialog)? I'm not sure, but the LTM may destroy and then re-create the
links ...

Alternatively, you can roll your own LTM. Basically you'd (a) determine what tables need to be relinked (generally done
by storing those values in a table somewhere), (b) run code to either refresh or rebuild the link. See here for more
info:

http://www.mvps.org/access/tables/tbl0009.htm

Thanks again for your reply.
Click to expand...

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
Back
Top