User Level Security

[Richard]

Hi

I am using user-level security for my database. When I open the db using
system.mdw, it prompts and says it doesn't have persmission to use the db.
True, but the application still opens.

How do I set it that if it is not opened using the workgroup, it will quit.

Many thanks in advance
Richard

 

[Arvin Meyer [MVP]]

You've done something wrong in your security setup. I suggest you read the
following:

Security FAQ
http://support.microsoft.com/download/support/mslfiles/SECFAQ.EXE

Lynn Trapp's summarization:
http://www.ltcomputerdesigns.com/The10Steps.htm

KB articles:
http://support.microsoft.com/default.aspx?scid=KB;en-us;q165009
http://download.microsoft.com/download/access97/faq1/1/win98/en-us/secfaq.exe
http://support.microsoft.com/default.aspx?kbid=325261

Joan Wild's articles:
http://www.jmwild.com/security02.htm
http://www.jmwild.com/security97.htm
http://www.jmwild.com/SecureNoLogin.htm
http://www.jmwild.com/Unsecure.htm

 

[Richard]

Hi Arvin

Thanks for taking time to reply.

Let explain it further. The application is now joined to a workgroup. By
right, if the ms access application is at default (ie. joined to the
system.mdw), it will not have the right to open the database, right?

So, I set up the access application to join the system.mdw workgroup and
open the database. It won't let me use the application but the front-end
application still open (i am using unbound forms).

I am trying to figure out how to close the application if the workgroup is
different instead of it opening and ususable.

Hope I explained myself.

many thanks
RIchard

 

[Richard]

Hi Arvin

Different way of looking at the question - How do I trap the application
error, ie when the database display the error "you do not have permission to
use ...."

i tried to trap the error using the first form to open, but it has not reach
that level yet..

Many thanks again
RIchard

 

[Rick Brandt]

Hi Arvin

Different way of looking at the question - How do I trap the
application error, ie when the database display the error "you do not
have permission to use ...."

i tried to trap the error using the first form to open, but it has
not reach that level yet..

You cannot. Any code or macro you would create to "trap" anything would
require that the file be opened so that the code or macro can be executed.
If the user has no permission to open the file then your trap can never be
executed.

 

[BruceM]

How did you set up the Access application to join the Sytem.mdw? Do you
mean System.mdw is the default workgroup as specified in Workgroup
Administrator?

Every Access database uses a workgroup file. By default this is System.mdw.
The workgroup file identifes you to the Access application, which specifies
the permissions the user or group has to that particular application. If
you do not specify otherwise, Access silently logs you in as the Admin user,
who by default is a member of the Users group and of the Admins group, which
means Admin has full permissions to all database objects and can administer
database permissions. In effect, the Admin user has unrestricted
permissions to the entire project unless you specify otherwise. Your
understanding about the default System.mdw file seems to be almost the exact
opposite of the way it works.

To specify otherswise you should create a new workgroup file. Make this
file the temporary default, and start the application. The general idea is
that in this new workgroup file you create users and assign them to groups.
In the Access application you use User and Group Permissions to assign
permissions to the groups. Be sure the Admin user is only in the Users
group, and remove most or all permissions from the Users group.

Important: Rejoin the default, untouched System.mdw file.

Open the database by way of a shortcut that inclues the full paths to the
Access.exe file, the mdb (or mde) file, and the new workgroup file. Any
Access application that has not been secured can be opened by double
clicking the file, or through the Access Open dialog. This is useful for
development, demonstrations, and so forth.

This is a very quick summary. The process has been well documented. The
links Arvin provided should prove helpful. One more that I found explained
it all very well was Jack MacDonald's Security Paper here:
http://www.geocities.com/jacksonmacd/
There are also links to an assortment of other security information.

 

[Richard]

Thanks to Rick and Bruce

I did some checking and it seems that the front end has not been secured,
the reason for it opening and the error for the 'no permission' is for the
back end.

Many thanks for your tips and help.

Richard