I created my own security code on database, that without entering right username or password, no body can enter. But entered person can close the form window and can access tables. I hide the tables by changing its name with prefix "Usys". and disabled the menu. But what if somebody knows how to use shift+enter thing and can access my tables. Is there any other method that prevents users to made changes to the table contents. Multi user enviornment, All should be able to add, modify, update through forms only, not directly to tables
Thanks in advance, Any help would be appreciated.
Consider implementing User Level Security. Google/search the forum for that keyword; there's several threads on how to implement ULS in any Access database.
Could you please explain it. or elaborate it. If we implement user level security. If we invoke all Add, Delete, update on table from user, It would apply that thing on the form as well. user wouldn't be able to make changes through the form too. please advice
User level security basically means you secure a database using a workgroup security file that defines what permissions a given user or group has to various objects. If properly secured, you can deny permissions for an average user to open or create tables while allowing him to use forms where you can control how data are validated and so forth.
Just so you know, VBA code won't necessarily stop a dedicated user trying to break the security and can be circumvented, whereas ULS is much more harder to circumvent.
Generally most day to day users of Access will not be able to interpret or circumvent the code , however as Banana has correctly pointed out, a dedicated and particularily malicious user may just do that.
Use the quick fix provided here if you wish - Though I would tend to agree that incorporating a ULS would be far more efficient, the quick fix provided should hopefully provide you with enough time to research ULS more thoroughly......
There is no "Easy way" to fully secure your database - it will take time, paitence and practise...
I recommend reading the following artical in its entirety....
Take your time and try not to become frustrated, only with experience will you learn all the aspects of Database creation.
I know personally that I myself have a long, long way to go....
Be very careful when setting up a ULS - it is easy to lock yourself out of the database if you do not follow everything absolutely perfectly.
It is true that ULS is the correct, formal and most secure way of protecting your database.... However it is also the easiest way of making mistakes, if you are not extremely careful.
Locking yourself out of your own database is no laughing matter.
Read a lot, take your time, take it one step at a time, test every step on a COPY of the database, Never edit the live database, keep several backups, use a front-end linked to a bank-end, set up a ULS, set unique users and passwords for every intended user and bite your tounge an awful lot.
Unfortunately, I have to agree with Skaas regarding his assessment that ULS is probably most easiest way to get yourself tangled up in the web of security and would second his suggestion that you take time to read through everything, and play with a throwaway database so you can understand the mechanism. I know I've been bit in the ass more than once with carelessly set-up ULS.
One more thing to consider: You indeed can disable the control box (and without code; it's in the Properties Windows, under Format tab, just need to scroll down a bit) but this may have the undesired effect of your users giving your application the three-fingered salute. You'll have to decide if this is worth the risk.
I worked on ULS over this week end. After so many tries I implemented it. You are right, experience and practice makes anybody perfect. Thanks to you guys I am learning even more.
