I have an orders admin database that is currently only accessed by two Sales Administrators. I have been asked to allow read only access to the DB for the actual sales force. Would it be better to create a new FE for them to access, or is there anyway that I can secure the existing file by user? I don't want to hard code in usernames.
-
-
Front End is always a good alternative for keeping the location of the tables hidden from users. -
There's no perfect way to achieve what you want in Access. The closest you can get is to put the backend on an undisclosed network location with a password. Create a front end MDE with all the database objects hidden and convert all the forms to access the tables as read only.
This can be compromised by looking at their active connections, say from a command prompt, to find the location of the server. Then they could go there and, worst case scenario, crack the password and change whatever they like. But if they had bad intentions, they could just delete the entire backend. It's unlikely that any of your users would have the technical knowledge to pull this off but it's something you need to be aware of. This is as secure as you can get with Access.Comment
-
Thanks chaps. I will go down the new FE route, and as Rabbit said, change all forms to read-only.
I had thuogh of this approach, but it is good to have it validated, so I don't waste my time running a fools errand. :)Comment
-
If you have the know how, you could use your intranet as a front end and serve it up with a web interface. This means creating all your forms from scratch though.Comment
Comment