W
W. Guy Delaney
I have spilt my database into a backend and frontend and have done what I
thought I needed to secure both the frontend and the backend.
Both the frontend and the backend use the same mdw file (KirkSecured.mdw).
Both the frontend and the backend have the same Groups--Admins, Users, and
KirkAdmin.
Both the frontend and the backend have the same users.
In both the frontend and the backend, the Admin user belong only to the
Users Groups.
In both the frontend and the backend, the Users group has no permissions.
I have a shortcut on my desktop that joins the database to the
KirkSecured.mdw workgroup. When I use this shortcut, I must enter a password
in order to open the database.
Here is my problem: When the database is in its normal state: that is, when
it is joined to the Secured.mdw workgroup, I can click on either the
frontend or the backend, leave the password window blank, click OK, and open
the either the frontend or the backend.
How frustrating! Any suggestions?
thought I needed to secure both the frontend and the backend.
Both the frontend and the backend use the same mdw file (KirkSecured.mdw).
Both the frontend and the backend have the same Groups--Admins, Users, and
KirkAdmin.
Both the frontend and the backend have the same users.
In both the frontend and the backend, the Admin user belong only to the
Users Groups.
In both the frontend and the backend, the Users group has no permissions.
I have a shortcut on my desktop that joins the database to the
KirkSecured.mdw workgroup. When I use this shortcut, I must enter a password
in order to open the database.
Here is my problem: When the database is in its normal state: that is, when
it is joined to the Secured.mdw workgroup, I can click on either the
frontend or the backend, leave the password window blank, click OK, and open
the either the frontend or the backend.
How frustrating! Any suggestions?