Link to home
Start Free TrialLog in
Avatar of Hankwembo Christopher,FCCA,FZICA,CIA,MAAT,B.A.Sc
Hankwembo Christopher,FCCA,FZICA,CIA,MAAT,B.A.ScFlag for Zambia

asked on

Creating Ms Access System tables

Hi All Experts

We are all aware that the MS Access is not all good where security is concerned, now for those who have created their own login forms for users, some will agree with me that we normally use a table with some basics columns in it as follows:

(1) PK
(2) User Name
(3) Password
(4) User rights

Normally this table is found in the BE .

My question is that , what is the danger  if we make this table as a System table and move it to the FE since we are able to lock navigation pane, cant this table much safer there? We are able to protect linked tables , queries and macros by locking the navigation pane , couldn't it be an opportunity to do the same with this login table?????

Regards

Chris
ASKER CERTIFIED SOLUTION
Avatar of Gustav Brock
Gustav Brock
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
To add on to Gustavs password comment, consider whether you truly need a password. E.g. if people are using your app from their own PC, you could get their username from the PC. I.e. if Anders is logged on to the PC, and Anders is in the user table, then he has access to use the App. That way we don't need the whole hazzle of storing a password (and resetting it when users forget).

I only truly see the need for a password if multiple people are sharing the same PC with the same login.
Hmm, well not in my eyes and it removes control over that table which is used for more than just log-in AND the advanced Access user could still get to it there since there is no way to truely lock the navigation pane.
Avatar of Hankwembo Christopher,FCCA,FZICA,CIA,MAAT,B.A.Sc

ASKER

You have made my day I cannot manage my happiness any more , who said the navigation pane can never be locked , please just read my article on protecting macros , link tables and queries you will learn how do to it for  free.

Regards

Chris
Thanks @Hankwembo Christopher

Yep, seen that code before and there is STILL a way to get to the navigation pane.  While the average user may not have access to the code or know how to use it if they do... and the advanced user will be able to unlock it. An advanced user will be able to if they want to.

The question comes down to what are you trying to protect.  If it's the code, you can put a password on that and no one will EVER see it without the password.  
The passwords? Then use SQL Server or Active Directory.
The objects?  Well that makes no sense because anyone can figure that out from looking at the forms
The data? It belongs to the company so if they are trying to prevent employee stealing their data they have another problem and they might want to deal with that because nothing can prevent an employee form simply using pencil and paper.
After locking the database with the lock you have seen just compile the database in accde that is it .
Next concern ?

The question comes down to what are you trying to protect.

I'm sure you are aware that normally the queries, macros and link tables are not protected by ACCDE , that is what need protection.





Regards

Chris