Workgroups and Access security 2

[WalkieTalkie]

I have put a secured MS Access database onto a network, where the front and back ends are both on a shared drive (because there is no access to the users' hard drives to put the front end).

As I understand it, the organisation's network has a number of servers, which users log into in a random basis.

My problem is that once the user has joined the workgroup associated with my database, Access then uses that workgroup for every other database that any other user wishes to open. The result is that they can't open their databases, because Access is asking for a username and password, and of course they do not have a valid username and password because they have not been given permission to use my database.

Does that make sense? I hope there is someone out there who understands and knows of a solution because it is a great big headache for me otherwise!!

Yours hopefully
Miranda

 

[JC3]

I am sorry to say that there is no easy way around this problem.

The best bet is to set up your own security by adding a users table to the database and having a form set up to verify the existence of the user and match the password.

You can also add a table of user groups in order to set up permissions. This will require some code, however.

 

[GDGarth]

Don't have the users join your workgroup. Instead, give them a shortcut (or put it on the server) that points them to the correct workgroup file (you use the /WRKGRP "Workgroup Name" parameter in the startup string.

I strongly recommend against setting up your own home grown security system. Access security works pretty well, and is more secure than anything you're likely to create.

 

[LittleSmudge]

The standard approach is to have all users have their System.mdw file to be the default file that ports with Access.

Then for special, restricted access databases on the network you have a central Xxxx.mdw file that contains all the User and Group information for the databases that need it.

Then users get into these restricted databases using a shortcut on their desktop. They need a shortcut on the desktop because the "Target" property in the shortcut needs to contain the following info

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "\\Sever\Path\Folder\DatabaseName.mdb" /user "theirUserName" /WRKGRP "\\Sever\Path\Folder\Xxxx.mdw"

The {/User "theirUserName" } bit is optional and just causes the log in dialog box to come up with their own name already typed in. - They still have to enter the password.




'ope-that-'elps.



G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.

 

[WalkieTalkie]

Thank you to all of you for this help. My next question is whether Access will revert back to the default system.mdw once the restricted database has been closed. I think I have found the answer (in the meantime) elsewhere - I understand now that as long as all users of Access make sure they are joined to the default system.mdw (by using the Workgroup Administrator - wrkgadm.exe), then I add the /WRKGRP switch to the command line of my shortcut, targeting my secure workgroup, then the problem will be solved? Have I got that right?
Thanks again
Miranda

 

[LittleSmudge]

Big TICK Miranda, - couldn't have explained it clearer myself !!


G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.

 

[WalkieTalkie]

Fantastic - thanks again for your help
Miranda

 

[kat25]

I'm not sure if I understand the shortcut command. Do
you use the quotation marks as shown in the example?
Could you give an example with real server/path info?
Thank you.



"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "\\Sever\Path\Folder\DatabaseName.mdb" /user "theirUserName" /WRKGRP "\\Sever\Path\Folder\Xxxx.mdw"

 

[WalkieTalkie]

Here is the command line that is working a treat for me (on my PC at home - no server yet)...

"D:\Program Files\Microsoft Office\Office\MSACCESS.EXE" "D:\Staff Training Database\SecureStaffTrainingDatabase.mdb" /user "MirandaW" /WRKGRP "D:\Staff Training Database\StaffTrainingDB.mdw"

Hope that helps

Miranda

 

[LittleSmudge]

IF you have a set up without any space characters in the server or path names then you do not need the quotes.

However, as Microsoft deem it appropriate to insert b1**6y space characters into standard folder names then it is usually necessary to include the quotes.

( For more info on why it is a good idea to avoid space characters in any Access object names wee FAQ700-2190 )
This applies to ALL windoz environment objects actually.





G LS
accessaceNOJUNK@valleyalley.co.uk
Remove the NOJUNK to use.