Back end not secured.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When you secure a split database, it appears the back end is not secured.
That is if you explore to the location of the backend, you can just double
click on it to open it. Have I applied the security incorrectly? Can I apply
the same security to the back end? That is somehow tie the .mdw file to
opening the back end directly as well?

Thanks for any advice.
 
Dylan Moran said:
When you secure a split database, it appears the back end is not secured.
That is if you explore to the location of the backend, you can just double
click on it to open it. Have I applied the security incorrectly? Can I
apply
the same security to the back end? That is somehow tie the .mdw file to
opening the back end directly as well?
Click to expand...
Open your secure front end, then close it but keep Access open. Open a new
blank database and import all of the objects from the unsecured BE.

HTH - Keith.
www.keithwilby.com
 
Hi Keith,

Did as you said and still the same. I opened my secure front end, then close
it but keep Access open. Open a new blank database and import all of the
objects from the unsecured BE. Then opened my front end and linked to my new
backend. But still the same result, no security on directly opening the
backend. Can you explain how your process applies the security to the new
backend.
 
Dylan Moran said:
Hi Keith,

Did as you said and still the same. I opened my secure front end, then
close
it but keep Access open. Open a new blank database and import all of the
objects from the unsecured BE. Then opened my front end and linked to my
new
backend. But still the same result, no security on directly opening the
backend. Can you explain how your process applies the security to the new
backend.
Click to expand...
Well that was just the starting block. I assumed that, since you'd secured
your FE that you'd know to remove permissions from the "users" group - did
you do that for all objects, including the "database" object?

Regards,
Keith.
www.keithwilby.com
 
Be sure that you are (a) using the right workgroup file, and (b)
logging-in as the user who you wish to own the database - not Admin.

(a) should be met automatically if you do as Keith suggested, & start
by opening the existing secured db.

HTH,
TC
 
Maybe I am confused, or wasn't clear in my initial post, but something seems
to be wrong.

I secured the database before I split it. I have a mdw file called
secured.mdw. When you use my shortcut to the front end (which uses the
/wrkgrp switch) , the front end opens with the login prompt. All is good so
far. The front end is linked to my backend (database_be.mdb). If you try
and open the front end directly (by double clicking on it), you get an error
message that you don't have permission to do this. This is the same
functionality I want when you double click on the backend (database_be.mdb).
But when you double click on the linked backed, it just opens with all the
tables to view. When I look at the workgroup administrator in the front end
all is good, linked to secured.mdw. However when I look at the workgroup
administrator in the backend, it shows the default system.mdw file. This is
not so good I assume. I don't want to "join" the backend to the secured mdw
as all other Access databases will then require this logon and I may have to
do this for all users. For the security, I have removed all permissions from
the users group. Set up two new groups and assigned permissions to these
groups, and then assigned users to the new groups.

How can I get the backend to produce the 'you dont have permission' error
message when a user double clicks on it?

Thanks for your assistance so far, I have followed to the letter but still
double clicking on the backend opens it up (noting that in the workgroup
administrator of the backend I am still linked to the default system.mdw and
no login prompt).

Any further assistance would be greatly appreciated. I hope I have made my
situation clear.
 
Dylan said:
Maybe I am confused, or wasn't clear in my initial post, but something seems
to be wrong.
Click to expand...

Anyone who is /not/ confused by Access security from time to time, is
fibbing :-)


I secured the database before I split it. I have a mdw file called
secured.mdw. When you use my shortcut to the front end (which uses the
/wrkgrp switch) , the front end opens with the login prompt. (snip) If
you try and open the front end directly (by double clicking on it), you
get an error message that you don't have permission to do this.
Click to expand...

Good so far.

But when you double click on the linked backed, it just opens with all the
tables to view. When I look at the workgroup administrator in the front end
all is good, linked to secured.mdw. However when I look at the workgroup
administrator in the backend, it shows the default system.mdw file.
Click to expand...

So clearly, the back-end is not secured. Did you use the database
splitter wizard? I have never used that wizard, but IIRC, it does not
secure the back end - the exact problem you are having.


Here is what I would do, myself. This does not use any wizards, because
I do not use the wizards. The aim is to get a new BE which is properly
secured & has the right permissions.

(untested)

1. Take a backup copy of each db (just in case).
2. Open the FE, logging-on as the *OWNER* of the FE db;
3. Delete the table links;
4. Import the actual tables from the unsecured BE;
5. Test thourougly, logging back in as various users, to ensure that
the security is exactly how you want it, in the now-unsplit db;
6. Log out & copy the unsplit FE; the copy is the new *BE*;
7. Check the new BE (which still contains all the forms etc.) can not
be opened with a normal double-click;
8. Open the new BE (logging on as any suitable user) & delete all the
queries, forms, reports, macros & modules;
9. Compact & close the new BE;
10. Open the unsplit FE, delete all the tables, then link to the tables
in the new BE.
11. Retest.

I feel that should work. If anyone else disagrees, hop in & say so!

HTH,
TC
 
Excellent TC. Love the work around. It made so much sense it had to work, and
...... it did!

Thanks very much, now have secured front and backends.

Cannot open either directly. Have to go throught my shortcut to the front end.

Excellent work.
 
Back
Top