How/Can you establish security logins from a menu button?

[Guest]

I have a complex database with multiple tables which has been primarily used
by myself. Now the database needs to be accessed by other departments. The
database when opened displays a main menu. From the main menu you can then
select which type of form to access (i.e. employees, non-employees, etc.).
Is it possible to put security on the menu options so to only allow access to
specific form views?

 

[Guest]

Hi,
there are a couple of different approaches to this.
You could use the build in user level security and assign users to groups
which have the specific permissions you want them to have. The build in user
level security can be a little bit confusing and challenging if you are just
starting so I would strongly suggest you read up on it before you try
anything. A good start is here:
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp
Another approach would be to implement some sort of custom security.
This would mean you set up a table with usernames and passwords and maybe
userlevel values if you want.
You can then use a login form to evaluate who is trying to get into the db
and what he/she should be allowed to see.
There is a good sample of this sort of security here:
http://www.utteraccess.com/forums/s...pe=m&olderval=&oldertype=#Post98966&bodyprev=
HTH
Good luck

 

[Guest]

Forgot to mention that in the case of this becoming a multi user database you
need to establish a true multi user environment!
What makes your database a multi user database? A split application is a
multi user environment. So what you need to do is split your application into
frontend (holding forms/modules/queries/reports) and backend (holding
tables). You can do this manually by creating a blank new database and
importing the one part and deleting it out of the other (which you need to do
if you applied build in user level security) and then relinking the two, OR
you can use the database splitter which is an easy tool which does this for
you automatically. You can find it under tools--database utilities--database
splitter. It will create two files out of your one mdb and seperates the
objects and creates table links in the frontend to link to the backend.
Now ones you have this split you need to give EACH user a copy of the
frontend. They should store it on their local drive. Then move the ONE
backend to the server/shared drive location which everyone has access to.
Now you just need to relink to this ONE backend from all the frontends since
the location obviously changed. You can do this by individually openeing the
frontends on the local users machines and using the link table manager. You
can right click on any table link in the database window and select link
table manager. This will pop up a new window showing the paths of all links
to the backend. Select them all, check the checkmark on the bottom to prompt
for a new location and press ok. Then browse to your new location where the
ONE backend is and press ok again. This will automatically refresh all the
table links. Then close and reopen the db and voila you should everything set
up the way you want.
This sort of setup is important in preventing corruption and performance
issues.
HTH
Good luck

 

[Guest]

Thanks very much for the information! Would you be able to use both security
methods (user level for the tables/queries/reports and custom security for
the form)? I'm thinking you could. As you suggested I'm an reading up on
user level security. I don't suggest trying to use it without reading the
article! Thank goodness I was working with a copy of the database!

 

[Guest]

Hi,
there is no real need to implement both.
The reason people use a custom solution rather then user level security is
either because they think it gives them more flexability or find ULS too
confusing. So either use one or the other depending on what you personally
like the best.
HTH
Good luck