Need Password for Command Button(s)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have created 5 command buttons with the name of each attorney on a form
that filters the cases for each individual attorney. Works fine, but now I
need to setup something within each command so the attorneys can not click on
the command of any other attorney. In other words I want each command button
to have some sort of password so no one else can access their filtered cases.
Please note that the attorneys want to just click on their button without
doing anything else so I was hoping there was a way I could code the command
buttons.
Joan
 
How about if they don't even have to use a command button?
You can filter what each sees by their Security logon id. If you are not
using Access security, use the Windows logon id.
 
So what you're saying is lawyers can't be trusted not to snoop into things
that are none of their business? I'm shocked I tell you, schocked! !:0)>
 
Hard to believe, isn't it?
But certainly, they are way too busy and important to do something as
pedestrian as actually entering a password. That would be expecting too much.

BTW, Target, Frrito, Putt Putt, and Lulu get very uncomfortable when they
are reading over my shoulder and see your signature line :)
 
BAD idea.
Different attorneys should be recognized upon logon to the database and only
shown their own data.

-Dorian
 
Why, Dave, do you perchance live in a cathouse? ;0)>

Actually I got the line from my very own Sneaky Pie Brown!
 
Sad that the replies I received were not only of no use, but anti-attorney as
well. This site is suppose to be helpful not a platform for the personal
views of those who reply. It may be difficult for some of you to comprehend
but everyone is not computer litierate nor do they wish to be. I respect
that and try to work around it. I wanted the help from this site that I have
received over the years: disappointed with your feedback. Wish Allen Brown
would reply.
 
Sad that the replies I received were not only of no use, but
anti-attorney as well. This site is suppose to be helpful not
a platform for the personal views of those who reply. It may
be difficult for some of you to comprehend but everyone is not
computer litierate nor do they wish to be. I respect that and
try to work around it. I wanted the help from this site that
I have received over the years: disappointed with your
feedback. Wish Allen Brown would reply.
Click to expand...

Dave Hargis offered a useful suggestion when he said
"How about if they don't even have to use a command button?
You can filter what each sees by their Security logon id. If
you are not using Access security, use the Windows logon id."

And I'm going to add something: If the lawyers are in a
partnership, they will be talking to each other about their
cases, getting opinions, deciding on strategies, etc. They
should have no problems seeing each other's cases.
 
Since the attorneys access the database that that contains the main form that
contains the command buttons through a workgroup pier-to-pier, they all open
the same main form so I am unsure that a security id would help.
Also, regarding your comments about the lawyers sharing client information
etc. that is not the reason that I need a security button. This law firm does
work as a team so that is not the issue. They are able to access all the
clients records in the database and the central files that are open to all
the staff. For some reason you have jumped to a wrong conclusion. The
reason I need a security code on the command buttons is for administrative
purposes.
Again, is it possible to put a security code on each of these buttons that
filter the individual files of the staff?
 
Since the attorneys access the database that that contains the
main form that contains the command buttons through a
workgroup pier-to-pier, they all open the same main form so I
am unsure that a security id would help. Also, regarding your
comments about the lawyers sharing client information etc.
that is not the reason that I need a security button. This law
firm does work as a team so that is not the issue. They are
able to access all the clients records in the database and the
central files that are open to all the staff. For some reason
you have jumped to a wrong conclusion. The reason I need a
security code on the command buttons is for administrative
purposes. Again, is it possible to put a security code on each
of these buttons that filter the individual files of the
staff?
Click to expand...
I don't jump to conclusions. I use deductive logic.

The easiset thing to do is to hide the buttons for all lawyers
except the one logged in.

this could be done by security id, or simply by checking which
computer is opening the form, assuming that the lawyers would
only want to access their files from their own computer.

If you really want to go with passwords at the button level, you
will need to create a table to hold the user's id or name, and
password.
Then you will need to code each button to open an inputbox, for
the password, determine who the user is so you can veryfy that
the password is valid for that particular user against the
table, then open the form if the password matches, or give an
failure message if it doesn't.

You will also need to code a form to allow users to change their
password, and another to add and delete lawyers.

then you have the issue of support staff who will need all
passwords or another method of seeing the cases.

It's a lot more complex than your original question implies that
you can handle.
 
Because all the users access Access via a workgroup pier to pier with my p/c
containing the form with the buttons, and the all also need to access all the
cases not just their own, I will need to find another solution. Perhaps just
do away with these command button and create one button with a parameter -
nuts, that won't work either. I give up.
 
PMFJI, but by "with my p/c containing the form with the buttons" do you mean
that everyone is using the same front-end to the data?

The application should be split into a front-end (containing the queries,
forms, reports, macros and modules), linked to a back-end. Every user should
have his/her own copy of the front-end, ideally on his/her hard drive.
 
Everyone does have Access installed on their hard drive. The software, but I
am the person who does all the data entry, run reports, etc.
So how would the data be updated on the back end? Staff also enters status
notes thru the workgroup on my Access.
 
In a properly set-up application, the front-end is linked to the back-end.
You do this to your copy of the front-end (through File | Get External
Data). To make sure that the link is a UNC, rather than uses a drive letter,
navigate to the database through the Network Neighborhood when linking it.
What this does is essentially put pointers to the real tables in your
front-end so the tables in the back-end are what are updated.

For more information, check what Tony Toews has to say on the subject of
splitting at http://www.granite.ab.ca/access/splitapp/index.htm
 
Because all the users access Access via a workgroup pier to
pier with my p/c containing the form with the buttons, and the
all also need to access all the cases not just their own, I
will need to find another solution. Perhaps just do away with
these command button and create one button with a parameter -
nuts, that won't work either. I give up.
Click to expand...
Is what you are trying to do is prevent a lawyer from CHANGING
another lawyer's cases?

Q
 
Back
Top