Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: "bass_player [SBS-MVP]" <bass_player@xxxxxxxx>
- Date: Sat, 11 Aug 2007 14:09:12 +0800
Use application role for your Access application and limit your SQL Server
roles and groups.
"Sean" <sean@xxxxxxxxxx> wrote in message
news:%23hWE4Py2HHA.1484@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
We have had instances where certain clued up individuals in our
organisation (one with an IT Degree), have engineered a way of getting
around the frontends to manipulate the data direct, this has caused some
problems with loss of data as the individuals concerned didn't know as
much as they thought they knew.
The DB Admin has asked me to look into a way of securing access through
the OS as he says that with the present access based system it just isn't
doable at a DB level.
Our DB Admin said they need to have permission to modify data in certain
tables, thing is we use Access frontends and these (I am informed) cannot
be locked down as Access (2000/2003 in our case) isn't that intelligent.
He asked for me too look into locking down ODBC at the users OS level, I
was wondering if anybody had any idea's about this or thought's about
locking it down at Access or SQL level that we may not already have
thought of.
FYI: Win 2K Domain, Win XP Pro Clients with mix of Access 2K/2K3
Cheers
Sean
.
- Follow-Ups:
- References:
- Prev by Date: Grant Insert Permission Freezing
- Next by Date: Re: Create table in schema
- Previous by thread: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Next by thread: Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Index(es):
Relevant Pages
|
|
