Security and Front-end/Back-end Database

  • Thread starter Thread starter Alan Jeffs
  • Start date Start date
A

Alan Jeffs

I have a database that is to have a front-end and a back-end. The plan is
to put the back-end in a shared area with each client running the front-end
on their local drive so that they can have their own selected options
without interfering with other clients. I want to apply Access security and
assign permissions to both the front-end (where the logic is) and the
back-end (where the data are).

I have been able to assign permissions with the database as a single entity
(not split) but I'm having problems doing it in the split configuration.
Which one to I assign permissions to: the front-end, the back-end or both?

Anyone have any suggestions?
 
I suggest securing the backend.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can lock
everyone including God out.

Practice on some copies to make sure you know what you are doing.

Use MDE files for the front ends so the user can't mess with them.
 
Thanks for this. I think it will help.

Joseph Meehan said:
I suggest securing the backend.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can lock
everyone including God out.

Practice on some copies to make sure you know what you are doing.

Use MDE files for the front ends so the user can't mess with them.

--
Joseph E. Meehan

26 + 6 = 1 It's Irish Math


Alan Jeffs said:
I have a database that is to have a front-end and a back-end. The plan is
to put the back-end in a shared area with each client running the front-end
on their local drive so that they can have their own selected options
without interfering with other clients. I want to apply Access security and
assign permissions to both the front-end (where the logic is) and the
back-end (where the data are).

I have been able to assign permissions with the database as a single entity
(not split) but I'm having problems doing it in the split configuration.
Which one to I assign permissions to: the front-end, the back-end or both?

Anyone have any suggestions?
Click to expand...
Click to expand...
 
Back
Top