Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: "Sean" <sean@xxxxxxxxxx>
- Date: Tue, 14 Aug 2007 13:18:58 +0100
thank you kindly
:)
"bass_player [SBS-MVP]" <bass_player@xxxxxxxx> wrote in message
news:%23PdhYVm3HHA.1164@xxxxxxxxxxxxxxxxxxxxxxx
http://www.sqlteam.com/article/using-application-roles
http://support.microsoft.com/kb/308312
"Sean" <sean@xxxxxxxxxx> wrote in message
news:OY1NpYb3HHA.5316@xxxxxxxxxxxxxxxxxxxxxxx
"bass_player [SBS-MVP]" <bass_player@xxxxxxxx> wrote in message
news:efm8k492HHA.4184@xxxxxxxxxxxxxxxxxxxxxxx
Use application role for your Access application and limit your SQL
Server roles and groups.
Hi BP,
Thanks for posting, can you be a bit more expansive about application
role or point me in the direction of a resource that can fill me in.
Cheers
Sean
.
- References:
- SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: Sean
- Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: bass_player [SBS-MVP]
- Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: Sean
- Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: bass_player [SBS-MVP]
- SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Prev by Date: Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Next by Date: Re: Rights to execute jobs?
- Previous by thread: Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Next by thread: Pros and cons of separate internal network
- Index(es):