Front End Linked Tables Aren't Secured

[Susan L]

To test splitting, I manually split a copy of my db into BE and FE. Security
had already been set up/is working. When I logged on as a user, I discovered
that I did not have permissions on the linked tables; the queries/forms,
etc., seem to have retained the permissions. Is it normal to need to reset
permissions for the tables? Haven't seen this mentioned anywhere as a
necessary step.

Now for the real novice question: Once the db is split, how do I create/or
otherwise work on tables in the BE. Create a shortcut to the BE?

 

[Joan Wild]

To test splitting, I manually split a copy of my db into BE and FE.
Security had already been set up/is working. When I logged on as a
user, I discovered that I did not have permissions on the linked
tables; the queries/forms, etc., seem to have retained the
permissions. Is it normal to need to reset permissions for the
tables? Haven't seen this mentioned anywhere as a necessary step.

No it isn't. Well... maybe. If you split manually, you deleted the tables
in the frontend and then created links to the tables in the backend. If you
set the permissions for 'new tables/queries' to be nothing, then the links,
when you create them will have no permissions on them. Perhaps that is what
happened.

Now for the real novice question: Once the db is split, how do I
create/or otherwise work on tables in the BE. Create a shortcut to
the BE? --

You can, or you can just create a desktop shortcut with
"path to msaccess.exe" /wrkgrp "path to secure mdw"

That'll open Access and use the secure mdw for that session. Any database
you open during that session will use the secure mdw.

You could also just use the frontend shortcut, and once in, hit Ctrl-O and
open the backend.

 

[Susan L]

Joan: I can't open your response to my question. ("Error on Page"). Could you
re-post your response?

 

[Joan Wild]

Here it is

To test splitting, I manually split a copy of my db into BE and FE.
Security had already been set up/is working. When I logged on as a
user, I discovered that I did not have permissions on the linked
tables; the queries/forms, etc., seem to have retained the
permissions. Is it normal to need to reset permissions for the
tables? Haven't seen this mentioned anywhere as a necessary step.

No it isn't. Well... maybe. If you split manually, you deleted the tables
in the frontend and then created links to the tables in the backend. If you
set the permissions for 'new tables/queries' to be nothing, then the links,
when you create them will have no permissions on them. Perhaps that is what
happened.

Now for the real novice question: Once the db is split, how do I
create/or otherwise work on tables in the BE. Create a shortcut to
the BE? --

You can, or you can just create a desktop shortcut with
"path to msaccess.exe" /wrkgrp "path to secure mdw"

That'll open Access and use the secure mdw for that session. Any database
you open during that session will use the secure mdw.

You could also just use the frontend shortcut, and once in, hit Ctrl-O and
open the backend.

 

[Susan L]

Thank you, Joan. ( I should say "again") I did have no permissions on new
tables, so they came in with no permissions. Since I have different
permissions for different groups, I'll just reset them in the FE.

Thanks for the tip on a shortcut to the secure mdw. That will solve a lot of
inconvenience for the person who administers the database. Thanks again.

 

[Joan Wild]

You're welcome. Just to clarify, the permissions you set on <new
tables/queries> doesn't affect whether a group/user can create new tables.
It just means those are the permissions they'll have on any new table/query
created. The exception is the owner of the new table/query - the owner
always has full permission, regardless of the permissions set.

 

[Susan L]

Joan: Thanks for the clarification. It will be a time-saver to put the basic
permissions on and then alter as needed for additional permissions.