Prevent Users from accessing backend database directly

[clmarks]

I have a database for which each user has their own copy of the front end. The backend sits in a central location on our network. I have just upgraded from Access 2003 to 2010 and find that, if you are in the backend, you can modify tables on the fly.

Is there a way to keep my users from being able to open the backend directly while still allowing them to link to the necessary tables?

Thanks,

Cherry

 

[gemma-the-husky]

seriously - why is it in a problem?

in most systems, you are likely to get the data exposed in some way. it has good points, as it provides independent means of accessing the data as well as bad.

the actual data and structure is often not so secret.

 

[boblarson]

You could use the Disable Bypass Key (do a search on that phrase) and then uncheck the Show Navigation Pane (or Database Window if in 2003 or earlier) and uncheck the Use Access Special Keys checkbox so F11 can't be used.

Then when you need in you will need to ENABLE BYPASS KEY and do your work and then disable again.

 

[Galaxiom]

seriously - why is it in a problem?

I propose on two counts. We are always telling developers not to allow users to access the tables directly and not to have multiple users in the same front end.

If one user can get in then two users can and then we have the database open simultaneously by two users. This is the BackEnd, the data, surely the worst possible place to have two users at once.

I also don't think it is good idea to have someone with the Back End open while users are connected via the Front Ends. I always lock my users our if I want to do anything in the backend. Am I just being paranoid?

I am leaning more and more to using SQL Server for the back end where the access by users can be tightly controlled.

 

[DCrake]

Depending on the sesitivity of the data in the back end, or as previously highlighted, not allowing people to open the back end directly the simplest solution is to password protect the back end as entry level. Then use the Link Table Manager to reconnect to the back end this time supplying the password. Then resdtribute the updated version.

I know there are password crackers out there. But day to day intruders can be dealt with in this way, the biggest being the managers who do not use the system as it should.

Once the links have been established the user will not be promted for a password at any time.

 

[clmarks]

My users are not particularly savvy about tables. I have had one employee who understood absolutley nothing but would open and tamper with everything. Needless to say, she is gone. But it does concern me that someone would start playing around with the table structures and do some damage.

Thanks for the responses. You have given me a lot to ponder. The people on this forum are really great.

Cherry