Now I am really lost - .Connect to secure Backend - still open???

  • Thread starter Thread starter Kahuna
  • Start date Start date
K

Kahuna

Hi folks, thought I'd cracked it but obviously not.

Got a front-end that links to backend using .Connect. Removed all but Open /
Run permissions on the backend and created a RWOP query to read / write the
linked tables in the front-end. Works great.

Problem is, the lower passwords are still able to open the backend and
change there own security on the protected tables, letting them read and
write the data directly?

Permissions in the front end are removed on the effected tables and only the
RWOP is allowing access that way.

How do I change permissions in the backend to prevent access to the security
tools? Any suggestions valued - getting close to temper time here!
 
Not sure what you mean by "Permissions in the front end are removed on the
effected tables". In a front-end/back-end structure, the permissions on the
back< end (the one containing the actual tables) are the significant ones
Click to expand...
in terms of restricting user access.

Does that help?
TC
 
Thanks TC (again)!

Discovered my issue was the lower passwords were still part of an Admins
Group which - though they had no specific permissions set - meant that they
could re-assign permissions themselves.

Solved thanks
 
When you split a database in a FE/BE config you must know that the BE does not ! take over the security settings
you put in the FE.
The new created BE database starts as an admin database with al the rights!
You are not ! the owner of this database as the creator.
You can cal this a BIG bug, assuming that you set up everything right........then you find out that
people access the BE database without any problems. (They are also logged in as Admin default).

You must know that your users are stored in the workgroupfile and the permissions are
stored in the actual database.

So securing a FE and also through the FE you try to set permissions on BE tables does not work!
You have to open the BE sepperatly with the workgroupfile.

Pieter (NL)
 
Back
Top