Split database front end security

[Guest]

I have a split database with the back end on a server. The mdw file resides
with the back end. I've followed Joan Wild's instructions for us poor souls
who used the splitter wizard and rebuilt the front end while connected to the
proper user's group. I want my users to pull a copy of the db onto their
computers. When they do, if I connect them to the right workgroup, the
security works fine. However, if they stay in their default group, it's as
though there is no security. How do I take away rights from the default
workgroup? Do I have to go to each individual computer?
I've also seen accolades about some of Joan's articles. Where can I find
these.
Thanks!

 

[Guest]

If security is properly defined the database can not be opened without the
corresponding workgroup file : redefine security.
--
***************************
If the message was helpful to you, click Yes next to Was this post helpful
to you?
If the post answers your question, click Yes next to Did this post answer
the question?

 

[Guest]

That's good to know. What exactly do you mean by redefine security? I've gone
so far as to create a new database (while connected to the proper user's
group), import all of my objects from the old, and set up security on it. If
I redefine it on the User's group on C drive, won't that just impact my
computer and not the other users?
Thanks.

 

[Guest]

Redefine security on the back end and front end on the server prior to
distributing the front end; you also need to define security on the server
directory.
--
***************************
If the message was helpful to you, click Yes next to Was this post helpful
to you?
If the post answers your question, click Yes next to Did this post answer
the question?

 

[Joan Wild]

You have missed a step, if they are able to open the mdb while using their
default system.mdw.

Unsecure it, and start over, following every step.

When you think you have it right, join system.mdw and see if you can open
the mdb - you shouldn't be able to.

Once you have it done right, you put the backend and the secure mdw on the
server. Give each user a copy of the frontend on their computer along with
a desktop shortcut to launch the secure frontend.

"Path to msaccess.exe" "path to secure frontend" /wrkgrp "path to secure
mdw"

 

[Guest]

Thanks Joan
Can you point me to a step-by-step? I followed one in a Roger Jennings book
I have that's been really good on most things, but obviously not here. Also
when you say unsecure it, do you mean through Group & user permissions?

 

[Joan Wild]

Login as a user that's member of the Admins Group. Grant full permissions
to the Users Group.
Use the Workgroup Administrator to rejoin the system.mdw that ships with
Access. Close and reopen Access and create a new mdb and import all objects
from the old.

You now have an unsecured mdb to start over with.

If I were you, I'd import the backend tables into this mdb as well. Follow
the step-by-step outlined in the security FAQ. I've outlined details at
www.jmwild.com/AccessSecurity.htm as well.

Once it's secured, don't use the splitter wizard. Instead split it manually
see http://www.jmwild.com/SplitSecure.htm

The security FAQ is at http://support.microsoft.com/?id=207793

 

[Guest]

Thank you!

Login as a user that's member of the Admins Group. Grant full permissions
to the Users Group.
Use the Workgroup Administrator to rejoin the system.mdw that ships with
Access. Close and reopen Access and create a new mdb and import all objects
from the old.

You now have an unsecured mdb to start over with.

If I were you, I'd import the backend tables into this mdb as well. Follow
the step-by-step outlined in the security FAQ. I've outlined details at
www.jmwild.com/AccessSecurity.htm as well.

Once it's secured, don't use the splitter wizard. Instead split it manually
see http://www.jmwild.com/SplitSecure.htm

The security FAQ is at http://support.microsoft.com/?id=207793