Securing a database with a BE

  • Thread starter Thread starter Alan Fisher
  • Start date Start date
A

Alan Fisher

I know this isn't the Security page but it is unavailable
right now. I want to secure all of my databases over the
weekend and have read MS's White Page. The questions I
have are:

1. Do I need to first recombine the back and front ends
then split them up after securing it.

2. I have three different front ends going to the same
back end, will that be an issue or will they work fine
once I secure them all?

3. I have one front end that goes to three separate back
ends, are there any issues there that I should be aware
of?

Any thoughts on how best to accomplish this? Thanks.
 
No-one can answer this unless you say what you are trying to achieve,
results-wise. For example, do you want to stop everyone from going directly
into your BE databases & reading the tables directly? If so, you can do that
with security, but you will have to rewrite parts of your code to use
so-called "Run With Owner Permission" (RWOP) queries, instead of accessing
the tables directly.

Access security is a significantly complex beast. There is no way you will
work it out in the space of 1 week-end.

HTH,
TC
 
Back
Top