Enter secure database via workgroup admin help please! A2k2

S

satdist

I have a secured, split, and Shiftkey disabled database that gives the
user an MDE file with a shortcut from the desktop. What can I do to
make certain a user doesn't follow the path in the shortcut to join the
mdw that protects the back end and open and view the data tables?
Thanks for any help here.
 
J

Joan Wild

I have a secured, split, and Shiftkey disabled database that gives the
user an MDE file with a shortcut from the desktop.

If you used the splitter wizard, then you'll find that the backend is now
unsecure. If you split it manually, you're OK.
What can I do to
make certain a user doesn't follow the path in the shortcut to join the
mdw that protects the back end and open and view the data tables?

You can use RWOP (run with owner permissions) for all data interaction.
Then you can remove all permissions on the backend tables.

You can also hide the backend - put it in \\servername\share$ rather than
\\servername\share. They won't be able to find it easily.

You can put an autoexec macro in the backend, that throws up a message, and
then quits.

And you can disable the shiftkey bypass in the backend.
 
S

satdist

Thank you for the response, I did secure the database manually.
As far as the back end goes, I can't use the explorer an navigate to
the back end file and open it. I can open Access go to the
Tools\Security\WorkGroupAdministrator\Join and find the location in the
shortcut and join the mdw I used to create the database. Then I can
navigate to the back end file and open it. Do any of your options
prevent this? Thanks
 
J

Joan Wild

If the users don't know the location of the backend, then they won't be able
to navigate to it - put it in a hidden share. Also, even if they do
discover the location, the autoexec will close the backend as soon as they
open it. And you can disable the shiftkey bypass in the backend to prevent
them from trying that.

Those measure should be sufficient to keep them out.

--
Joan Wild
Microsoft Access MVP
Thank you for the response, I did secure the database manually.
As far as the back end goes, I can't use the explorer an navigate to
the back end file and open it. I can open Access go to the
Tools\Security\WorkGroupAdministrator\Join and find the location in the
shortcut and join the mdw I used to create the database. Then I can
navigate to the back end file and open it. Do any of your options
prevent this? Thanks
 
S

satdist

Thank you very much.....that will do the job. Do you have any links to
building the autoexec that you suggest?

Joan said:
If the users don't know the location of the backend, then they won't be able
to navigate to it - put it in a hidden share. Also, even if they do
discover the location, the autoexec will close the backend as soon as they
open it. And you can disable the shiftkey bypass in the backend to prevent
them from trying that.

Those measure should be sufficient to keep them out.
 
J

Joan Wild

I don't have a link, but it's fairly straight forward:
New macro - save it with a name of Autoexec
Action: MsgBox
in the lower pane put whatever message you'd like to appear e.g..
Please use the frontend application

Second Action: Quit
 
S

satdist

BINGO! Your awesome.....thanks much.


Joan said:
I don't have a link, but it's fairly straight forward:
New macro - save it with a name of Autoexec
Action: MsgBox
in the lower pane put whatever message you'd like to appear e.g..
Please use the frontend application

Second Action: Quit
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top