![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
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. |
#3
| |||
| |||
|
#4
| |||
| |||
|
|
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 *** |
#5
| |||
| |||
|
|
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. |
#6
| |||
| |||
|
|
Security is a database engine issue, not a front-end issue. |
![]() |
| Thread Tools | |
| Display Modes | |
| |