Need help with Security Step by Step Last steps

[Guest]

Ok. I set the security step by step today.
I have set up the new workgroup file in a different drive than my "C" drive,
so I'm not sure if that's what the issue is when I try to do the last steps
where I creat a shortcut on my desktop.
When I set up the short cut & open it. The MSys files are there for my
database. Is this correct?
Then as it states in the instrutions, I cannot open my secured database.
So, do I go back to Access Security & join to the workgroup file I created
in order to open my secured database?
Also, how do I set up my users with desktop access to the database? I'll of
course do that after I split the database. But I wanted to practice before
splitting the database just to be sure it works.
Thank you for your help.

 

[Scott McDaniel]

Ok. I set the security step by step today.
I have set up the new workgroup file in a different drive than my "C" drive,
so I'm not sure if that's what the issue is when I try to do the last steps
where I creat a shortcut on my desktop.
When I set up the short cut & open it. The MSys files are there for my
database. Is this correct?

Not sure what you mean - do you mean the MSys files are in your Access database? If so, then yes, all Access files
should have the various MSys files.

Then as it states in the instrutions, I cannot open my secured database.
So, do I go back to Access Security & join to the workgroup file I created
in order to open my secured database?

You can do this, but you'll be better off building shortcut that will open your database with the correct workgroup.
Build a desktop shortcut and use this as the Target:

"Path to MSACCESS.EXE" "Path to your database" /wrkgrp "Path to your workgroup file"

If you join the workgroup file, then that file is used for every Access session on your desktop; typically, you'd want
to keep the default System.mdw file as your default workgroup.

Also, how do I set up my users with desktop access to the database? I'll of
course do that after I split the database. But I wanted to practice before
splitting the database just to be sure it works.

Typically you would provide users with a shortcut like described above. They must all use identical (or the same)
workgroup files; many people put the mdw file in the same directory as the backend datafiles; others distribute the mdw
file for users to join locally.

Also, most developers distribute a frontend to each and every user.

Thank you for your help.

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

 

[Joan Wild]

Also, how do I set up my users with desktop access to the database?
I'll of course do that after I split the database. But I wanted to
practice before splitting the database just to be sure it works.

[/QUOTE]


Just an additional comment on splitting. You don't want to use the database
splitter wizard on a secure mdb as that will result in a secure frontend,
but a completely unsecure backend. Instead, split it manually -
www.jmwild.com/SplitSecure.htm

 

[Guest]

So, to place the secured database FE on each user's desktop, I will need to
develop the shortcut you described on each user's desktop?

I'm ok with that, however, I don't want the user to have to type in a
password to open the database. They have "read only" access anyway, so how
do I give them access w/o a password?

Thanks for all your help. This security set up is driving me crazy!

 

[TC]

So, to place the secured database FE on each user's desktop, I will need to
develop the shortcut you described on each user's desktop?

Yes.

HTH,
TC (MVP Access)
http://tc2.atspace.com

 

[Scott McDaniel]

I'm ok with that, however, I don't want the user to have to type in a
password to open the database. They have "read only" access anyway, so how
do I give them access w/o a password?

When you say "read only" access, you mean through the ULS and not through Windows permissions? All users must have
read/write permissions on the file and folder hosting the backend database.

To enter the password automatically, you can include the username and password in the shortcut's Target:

"Full Path to msaccess.exe" "full path to your db" /wrkgrp "full path to your workgroup file" /user "Your UserName" /pwd
"Your Password"

This carriers with it the obvious security implications - any user can rightclick the shortcut and get the login
credentials, basically making ULS ineffective.

There are other command line switches; see the Access online help for info under the "Startup Command-line Options"
topic




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

 

[Joan Wild]

So, to place the secured database FE on each user's desktop, I will
need to develop the shortcut you described on each user's desktop?

Yes, however...

I'm ok with that, however, I don't want the user to have to type in a
password to open the database. They have "read only" access anyway,
so how do I give them access w/o a password?

All users need full permissions on the folder where the database is located.
If you don't want users to have to login, and as long as you have only one
group of users, you can secure it so that they don't have to login. Just
grant whatever permissions you want them to have, to the Users Group. Then
they can just open the mdb using their default system.mdw. No shortcut
required then.