FE and BE security

T

Todd

I know this question has been asked but I secured by dbase
and then split it. The FE is secured but the BE is not.
Why wouldn't the BE be secured as well when I already
secured the dbase originally. Also, what is the process
to secure the BE now? Help!
 
J

Joan Wild

The database splitter wizard creates a new database for the backend and
imports the objects from the frontend. Imported objects always lose their
permissions.

You could have split it manually after securing, and avoided this.

To secure the backend now, join your secure mdw workgroup. You could just
open your secure frontend (you'd be using your secure mdw to do this), and
log in as the user who you want to own all objects. Create a new database
and import all objects from the backend. Then go to Tools, security,
permissions, and remove all permissions for the Users Group, and for the
Admin User. Then set the permissions you want your groups to have for the
database and table objects.

This new database will be your new backend. Delete your old one and rename
this one to suit.
 
T

Todd

Sorry for my lack of knowledge on this but are you saying
to log in to my front end (with my administrator login)
and while I'm logged in create a new database? How do I
create one while I'm in my FE?
 
J

Joan Wild

Yes that's what I mean. Use File, New or Ctrl-N.

Post back if you've disabled these.
 
T

Todd

I did what you said and made a new backend. Even after I
changed the permissions on the back end I could still open
the backend without even logging in. Now, if I set the
permissions of the backend to read data only I can't
change the information within the tables but by doing that
when I try to enter data from the front end I can't
because it is read only. I want my user to be able to
update, insert, and delete records from the front end but
not randomly open the back end and do it.

Can the backend be secured the same way as the actual
front end (i.e. at least a log on)?
 
J

Joan Wild

Todd said:
I did what you said and made a new backend. Even after I
changed the permissions on the back end I could still open
the backend without even logging in.

Then you are doing so using the standard system.mdw file; you shouldn't be
able to even open it using that workgroup. Likely the Users Group still has
open permission on the database object, or the Admin user owns the database.
Double check these.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top