Using NT to secure Access db

[oharab]

I have built several Access Apps for the company I work for and have 'secured' them in different ways.
Some use full MS Access User Level Security, others a faux security using tables in the database. I don't like the idea of having to log on to systems after first logging on to the network, so I was wondering what the consensus of opinion was in this forum on the security provided by NT.
What I intend to do not put any restrictions on opening the database (front end file) but have the data (back end) file in a folder on the LAN which I can control access to using standard NT security and user groups. The user can open the db, but not do anything when he gets there! By setting permissions carefully I should even be able to make one group of users read only & another read/write.
Is this a sensible way forward? Is NT security adequate in this situation? What think you all?

Cheers

Ben

----------------------------------------------
Ben O'Hara

http://www.RobotParade.co.uk

"Where are all the stupid people from...
...And how'd they get so dumb?"

NoFX-The Decline
----------------------------------------------

 

[endwarde]

I did this with a database that I put together for my company a few years ago. Different parts of the database were needed by different departments, so I divided up each section of the data into modules (with different permissions) which I then linked together for the final database. It worked like a charm.

 

[KenReay]

Hi

Like you I dislike the principle of having two log ins, I have used various methods in the past to 'build' security using the NT login plus various Access options. While my techniques have usually been enough to keep nosey users at bay, they would not defeat a reasonably knowledgeable person. Indeed nor would your suggestion, since they could simply copy the mdb to another location (where they had permissions) and would then have free access to all data, but admittedly they (perhaps) could not update the data in its original location. I am not an expert on NT and NT User permissions, but as I understand it users must have Create and Delete permissions (at least)in the directory in which the backend is located, in order for them to create and delete the lock file. Although I have never tried this, I haev often contemplated the possibility of linking the NT login to the Access permissions in some way, either by linking the NT Login id to Access Security groups via a table, or by perhaps mimicing a log in code. It has nevr got beyond the thinking about it stage and I haev no idea if it could be done or how (anyone done it out there?).

Regards

Ken Reay
Freelance Solutions Developer
Boldon Information Systems Ltd
Website needs upgrading, but for now -

http://www.kenneth.reay.btinternet.co.uk

UK