How to Lock Tables on the BackEnd .mdb file

[RLN]

RE: Access 2003

My users have an .MDE as their front end.
With this .mde they can still get to the container, double click a
table, and modify data on the back end.

What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?
*** Sent via Developersdex http://www.developersdex.com ***

[Chris O'C via AccessMonster.com]

Upgrade the back end to SQL Server Express and apply security from there.
Use only stored procedures to retrieve, update and delete data.

Chris
Microsoft MVP
RLN wrote:

>What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200807/1

[Tom van Stiphout]

On Sat, 26 Jul 2008 01:17:49 GMT, "Chris O'C via AccessMonster.com"
<u29189@uwewrote:

The OP wanted to know how to prevent people from getting to the data.
Wouldn't running a stored proc that selected from the table be enough
to "get to the data"?
And for that matter, running the Update sproc be enough to alter that
data?

-Tom.
Microsoft Access MVP

>Upgrade the back end to SQL Server Express and apply security from there.
Use only stored procedures to retrieve, update and delete data.

Chris
Microsoft MVP
RLN wrote:

>>What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?

[Tom van Stiphout]

On Fri, 25 Jul 2008 22:10:33 -0700, Tom van Stiphout
<no*************@cox.netwrote:

I meant to add: of course this assumes they have access to that data
in the first place. Maybe I misunderstood the OP's scenario.
OP, can you clarify: does the user have access to the data when using
the application?
(if the answer is Yes, I'm leaning towards RWOP queries)

-Tom.

>On Sat, 26 Jul 2008 01:17:49 GMT, "Chris O'C via AccessMonster.com"
<u29189@uwewrote:

The OP wanted to know how to prevent people from getting to the data.
Wouldn't running a stored proc that selected from the table be enough
to "get to the data"?
And for that matter, running the Update sproc be enough to alter that
data?

-Tom.
Microsoft Access MVP

>>Upgrade the back end to SQL Server Express and apply security from there.
Use only stored procedures to retrieve, update and delete data.

Chris
Microsoft MVP
RLN wrote:

>>>What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?

[Chris O'C via AccessMonster.com]

If you read his earlier question, he's concerned with users changing the data
in the tables manually. It looks to me like he wants them to use only his
app to show, update and delete data.

Chris
Microsoft MVP
Tom van Stiphout wrote:

>The OP wanted to know how to prevent people from getting to the data.
Wouldn't running a stored proc that selected from the table be enough
to "get to the data"?
And for that matter, running the Update sproc be enough to alter that
data?

-Tom.
Microsoft Access MVP

>>Upgrade the back end to SQL Server Express and apply security from there.
Use only stored procedures to retrieve, update and delete data.

[quoted text clipped - 4 lines]

>>>What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200807/1

[Chris O'C via AccessMonster.com]

He asked for the best way. Access user level security isn't in that category.
Chris
Microsoft MVP
Tom van Stiphout wrote:

>(if the answer is Yes, I'm leaning towards RWOP queries)

>>>>What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200807/1

[lyle fairfield]

On Jul 25, 11:50 am, RLN <[e-mail]:

RE: Access 2003

My users have an .MDE as their front end.
With this .mde they can still get to the container, double click a
table, and modify data on the back end.

What is the best way to lock the tables on the back end .mdb so they
cannot get to the data?

Hide the DataBase window?