By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,704 Members | 1,944 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,704 IT Pros & Developers. It's quick & easy.

How to Protect your Back End?

100+
P: 365
Good aft peeps,

im investigating the FE/BE access route just as a time filler really (dont get out much - LOL) just wondered how people protect their BE databases?

Dan Out
Jan 29 '09 #1
Share this Question
Share on Google+
8 Replies


Expert 100+
P: 1,287
First, I hid the navigation window. Didn't feel too secure.
Then, I put in code that checks the windows login name and closes the db if it's not me. I like that better.
Finally, I renamed the backend from .accdb to .accdr. Now if anyone opens it and it doesn't close, they see the runtime menu and all they can do from the menu is close Access. I honestly don't think any of the users would imagine changing the file extension.
Jan 29 '09 #2

100+
P: 365
@ChipR
mine uses .mdb extension i believe?
Jan 29 '09 #3

Expert 100+
P: 1,287
Ah, I'm using the 2007 format, so .accdr files automatically use the Runtime environment even though my users all have the full version of Access. I don't know whether this was an option before the 2007 version.
Jan 29 '09 #4

100+
P: 365
not sure, i have an alternative of my own, using the Command line switch /cmd and setting a value so that if there is no value it closes, ie you need to know the right answer, but it still leaves the back end to "foreign" update queries, if you know what i mean....

Dan
Jan 29 '09 #5

Expert 100+
P: 1,287
Yeah I hadn't though about that. How can you prevent another front end from linking to and updating your tables if they know the structure?
Jan 29 '09 #6

100+
P: 365
or that yeah, the ideal would be to use a database password, but you cant code that in AFAIK... or can you?
Jan 29 '09 #7

DonRayner
Expert 100+
P: 489
If you are using the access user level security on the frontend you can bring the backend into the same workgroup with the frontend. That way you can set whatever permissions on the tables that you want.

Lately I've taken to outputing my frontend as an mde and using sql express as my backend. That way I can use the windows login ID to set access levels to the db.
Jan 29 '09 #8

100+
P: 365
@DonRayner
im not using this because i couldnt be bothered and it wouldnt fit in with my custom "ness"

@DonRayner
this gives me an ingenious idea... the BE will be located in a domain server so i can set the permissions to deny access to all but me, im sure that would work... ill have to try it tomorrow

any other ideas very welcome.

Dan
Jan 29 '09 #9

Post your reply

Sign in to post your reply or Sign up for a free account.