Exactly Roy,

It is a drag but, it does allow you to concurrently work with multiple

secured

databases and not be restricted to only those using the same workgroup file.



Althought not recommended, if you are relatively comfortable with the

security

of your PC, (i..e. NT...) you can include the appropriate account and

password

information into the shortcut line too.  Not recommended UNLESS you are

comfortable with your work environment security.  Many would view PC

security

as an oxymoron especially since 'crackers' are readily available to extract

Access workgroup accounts/passwords.  Passwords, like padlocks, really just

keep honest people out.



Tom Hamilton

T_Systems, Inc

Database Programmer

(xxx) xxx-xxxx



>>> Pardee, Roy E 03/05/01 07:15AM >>>

This behavior is a drag, but there is a way around it.  Rather than using

the workgroup administrator utility to join the workgroup defined in the

.mdw file with your account definitions, you stay with system.mdw and

instead reference the workgroup file on a shortcut command line with the

/wrkgrp switch.



So you give your users desktop shortcuts to your app, and on the shortcut's

Target you put:



<<path to MSAccess.exe>> <<path to your .mdb file>> /wrkgrp <<path to your

.mdw file>>.  For instance



"C:\Program Files\Access2000\Office\MSACCESS.EXE" "P:\MyDir\MyDatabase.mdb"

/WRKGRP "P:\MyDir\Secured.mdw"



HTH,



-Roy



-----Original Message-----

From: pmcmillin@m... 

[mailto:pmcmillin@m...] 

Sent: Monday, March 05, 2001 6:37 AM

To: Access

Subject: [access] Re: Access Permissions





I have a question regarding this issue also...



When you set this up on the computer it applies to Access as a whole and 

not just that one database, right?  We tried setting this up in one of my 

college database classes and had great difficulty.  Because it changes one 

of the system files, it applied to Access.  So that anytime any one opened 

up Access on that computer it prompted you for a userid and 

password.  What's up with this?





At 10:21 AM 3/5/2001 +0000, you wrote:

>What a nightmare ! I would really appreciate some expert help on this

>one....

>

>I have set up an Access database which will (in time) be accessible from

>various PCs on a network. Simple enough. At the moment, however, there is

>only one PC, used by 4 people.

>

>I would like to set up user groups allocating various permission levels

>(delete, insert, update etc..) as appropriate. When a user opens up the

>database on the PC, he/she enters their username/password and uses the

>database with the appropriate permissions. Then when they are finished,

>they close the database, and another user can come on enter their details

>and use the database with their permissions etc.. etc..

>

>I wouldn't have thought this was too difficult to achieve and the Access

>help strongly implies this is so. However I CANNOT get Access to behave

>like this. The central question is - how do you change the user of a

>database under this scenario ?

>

>There are 2 ways of setting permissions - directly via Tools|Security

>etc.. - or by using the User-Level Security Wizard, which secures the

>database and creates a backup.

>

>Method 1 lets you add users to groups, however if you want to set

>individual passwords to each user - it only appears to let you do this for

>user 'admin'.

>

>That aside, once entered, all the information - new users, permissions

>etc.. - appears to have been "taken" by the database.

>

>However, when you close it and open it again there is no user/password

>dialogue box in sight - it just takes you straight back in - as

>user 'admin'. How do you go in as another user - and hence with the

>appropriate permissions ?

>

>Method 2 - the User-Level Security Wizard - seems thorough and lets you

>assign new users (and passwords this time) to groups. However when you

>close and come back in there is (again) no username/password dialogue box

>and it takes the current username as the one entered in when you log on

>into windows.

>

>This implies that by different 'users', Access actually means different

>computers (if so why on earth doesn't the Help facility say so and save

>newbies like myself hours of wasted effort!).

>

>However, maybe everyting is set up and the user log-on just needs to

>be 'turned on' somewhere else.

>

>Perhaps there is a good on-line resource (not Microsoft-based please!)

>someone can point me to.

>

>

>Thanks in anticipation of your help....

>

>

>

>Simon G

>

>