> Any idea what is going wrong and how I can fix it?
Well, you never did have to use the security wizard to secure a database.
The security wizard does not do anything that you can't do manually (it does
not modify the file in some special way).
So, really just make sure you launch ms-access joined to that workgroup.
Create a new blank database (while still joined). Remove database
permissions to the "users" group. And, remove permissions from the Admin
"user". (that means you have to be logged in with a different user name then
admin....
I assume you have a some admin user account logon for your current secured
database. Now, simply import all of the back tables into this new mdb. Since
you removed all permissions to the "users" group for the database, and also
from the admin USER logon. If you then try and launch this database not
attached to the correct workgroup, you get a security message.
I actually have several split applications, and I never did get around to
security the back end. (security in the front end is only restricted to what
reports and forms particular users can launch). For the back end:
So, I make a macro called AutoExec. In the macro, I put the following code:
Action Parms
Msgbox message:You do not have permissions to run this file
Beep: Yes
Type: Critical
Title: Can not run
Quit: Options:Exit
As an alterative, you an make a nice little form in the back end, and set
the start-up options to run that form that displays a message, and then when
they click ok...you do a application.quit.
And, to disable the "shift key", simply grab my shift key utility here to
turn off the shift key by-pass
http://www.members.shaw.ca/AlbertKal.../msaccess.html
This actually keeps 99% of the people out. If they double click on the back
end...they get a security message. And, even better is that they get this
message EVEN WHEN connected to the correct security group.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
(E-Mail Removed)
Similar Threads
