SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- From: "Sean" <sean@xxxxxxxxxx>
- Date: Fri, 10 Aug 2007 08:56:31 +0100
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:
- 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?
- Prev by Date: Re: Create table in schema
- Next by Date: Pros and cons of separate internal network
- Previous by thread: Re: Create table in schema
- Next by thread: Re: SQL DB with legacy Access Frontend - How do we stop people getting in through the backdoor?
- Index(es):