PLEASE HELP.Locking buttons out on a multi user form

[Army MI]

I have a database in which i have 6 users. But i am haveing problems i have
enabled the security and assigned each user a name and password but i cant
figure out how to design it so that if user one logs on he only has a select
few buttons he can click on. I have tried using the visablility option but
it applies it to all of the users. does anyone have an idea or should i
explain further?

 

[golfinray]

If your database is on a lan, and I assume it is, is it split? If not, it
need to be. Splitting the database in Front End (FE) and Back End (BE) makes
what you are trying to do mush simpler. Your tables are on the BE on your lan
and everything else is on each user's computer. You can load the FE on each
user's computer with only the forms and reports you wish them to have. Is
this the way you are set up now?

 

[Army MI]

No its not. I am pretty proficient with Access but how do i go about doing
this?

 

[Arvin Meyer MVP]

If you have enabled security, you can use:

CurrentUser()

function to identify users. Now, with only 6 users, you could use a Select
Case statement, but if you anticipate more users, you probably should build
a table with a security level based upon each user, then do a lookup in the
form's open event and decide which buttons to hide/show.

 

[John W. Vinson]

No its not. I am pretty proficient with Access but how do i go about doing
this?

Golfinray is quite right, for this and many other reasons.

See http://www.granite.ab.ca/access/splitapp.htm for a thorough discussion of
the need and technique for splitting.

 

[Arvin Meyer MVP]

Splitting the database should be done with all multi-user databases as per
the other's recommendations. Do it as soon as possible to avoid possible
corruption, particularly if you are trying to change how each user sees the
form. That will not solve your immediate problem though since each user is
now opening his/her own instance of the database. What happens when they
close though is that it tries to save certain characteristics to the
registry and will get a different instance when they open the next time. The
combination of saving and opening between users can cause corruption.
Splitting, and putting a separate copy on each workstation avoids that. You
still need to implement the procedures I suggested earlier. Then
redistribute the front-end.