dbTalk Databases Forums  

Read only linking

comp.databases.ms-access comp.databases.ms-access


Discuss Read only linking in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
bobh
 
Posts: n/a

Default Read only linking - 06-25-2010 , 03:39 PM






Hi All,

With a split db is there code that could be added to the back-end that
would make/limit any links from is point forward 'read only' ?? I
would want the links into the front-end to be read/write.

anyway to make links read-only using Access jet? or do I have to move
the back-end to SQLServer to get that kind of control.

thanks
bobh.

Reply With Quote
  #2  
Old   
Banana
 
Posts: n/a

Default Re: Read only linking - 06-25-2010 , 04:01 PM






On 6/25/10 1:39 PM, bobh wrote:
Quote:
Hi All,

With a split db is there code that could be added to the back-end that
would make/limit any links from is point forward 'read only' ?? I
would want the links into the front-end to be read/write.

anyway to make links read-only using Access jet? or do I have to move
the back-end to SQLServer to get that kind of control.

thanks
bobh.
Unfortunately, there is no easy way to make linked tables read-only and
using a server-based RDBMS with permissions set would probably be the
best way.

A possibility is to use ULS and grant the Users read only permissions.
That assumes you are using a .mdb file format (which can work very well
even in Access 2007 and 2010). If it's setup correctly, it won't be
necessary to require joining a workgroup unless additional permissions
is needed.

An unofficial way is to put the backend in a read-only folder but I
understand it causes more problems than it solves.

HTH.

Reply With Quote
  #3  
Old   
Rich P
 
Posts: n/a

Default Re: Read only linking - 06-25-2010 , 04:05 PM



You can control the tables with Access Security. You can also lock the
tables (with Access Security) and use only forms as the user interface
and control data access through the forms. But if you are in a
multi-user environment and if the data is real sensitive and you need
real strong security - then it would be time to step up to a
non-integrated development environment (.Net).

Rich

*** Sent via Developersdex http://www.developersdex.com ***

Reply With Quote
  #4  
Old   
Tom van Stiphout
 
Posts: n/a

Default Re: Read only linking - 06-26-2010 , 12:19 PM



On 25 Jun 2010 21:05:09 GMT, Rich P <rpng123 (AT) aol (DOT) com> wrote:

I disagree with that. .Net would be used to develop the front-end. If
you keep the data in Access it is still just as unsecure as with an
Access front-end.
Secure data requires a server DBMS such as SQL Server. Then the front
end can be anything you want; the back-end will ensure the data is
secure.

-Tom.
Microsoft Access MVP


Quote:
You can control the tables with Access Security. You can also lock the
tables (with Access Security) and use only forms as the user interface
and control data access through the forms. But if you are in a
multi-user environment and if the data is real sensitive and you need
real strong security - then it would be time to step up to a
non-integrated development environment (.Net).

Rich

*** Sent via Developersdex http://www.developersdex.com ***

Reply With Quote
  #5  
Old   
David W. Fenton
 
Posts: n/a

Default Re: Read only linking - 06-26-2010 , 04:52 PM



Tom van Stiphout <tom7744.no.spam (AT) cox (DOT) net> wrote in
news:sgdc261u0iupqdocmk5m9cib8tdpidns8t (AT) 4ax (DOT) com:

Quote:
On 25 Jun 2010 21:05:09 GMT, Rich P <rpng123 (AT) aol (DOT) com> wrote:
You can control the tables with Access Security. You can also
lock the tables (with Access Security) and use only forms as the
user interface and control data access through the forms. But if
you are in a multi-user environment and if the data is real
sensitive and you need real strong security - then it would be
time to step up to a non-integrated development environment
(.Net).

I disagree with that. .Net would be used to develop the front-end.
If you keep the data in Access it is still just as unsecure as
with an Access front-end.
Secure data requires a server DBMS such as SQL Server. Then the
front end can be anything you want; the back-end will ensure the
data is secure.
Let me second that:

Security is a database engine issue, not a front-end issue.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

Reply With Quote
  #6  
Old   
Tony Toews
 
Posts: n/a

Default Re: Read only linking - 06-26-2010 , 06:06 PM



On 26 Jun 2010 21:52:12 GMT, "David W. Fenton"
<XXXusenet (AT) dfenton (DOT) com.invalid> wrote:

Quote:
Security is a database engine issue, not a front-end issue.
Agreed. As part of that anyone can copy an Access database file from
the server and put it on a thumb drive and take it home with them. Or
zip and place it on Skydrive or email or whatever.

Tony

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.