In your first post, you said " ... goes to two different switchboard forms
base on the type of user (manage or employee)." Therefore, you already have
some means of identifying which type of user is logged in. How are you
doing that? Please post the code you are using for that, and we'll go from
"dcash45" wrote in message
> Hi Rob thanks for replying but Im still a little lost. Yos said I should
> a IsManager function but I didnt have one. So I designing it right now
> but I
> dont really know what I should include.
> "Rob Parker" wrote:
>> Since you can already determine whether the type of user, I'll assume
>> you have a function (IsManager in the following lines) that returns True
>> the user is a manager.
>> In the Open event of your form(s), you can enable/disable various
>> as follows:
>> Me.MyAddButtonName.Enabled = IsManager
>> You can also set the form properties to allow edits/additions/deletes in
>> same fashion:
>> Me.AllowEdits = IsManager
>> "dcash45" wrote in message
>> > Hello I want to open a form and enable or disenable the buttons base on
>> > what
>> > type of user is login.
>> > I have a login form that goes to two different switchboard forms base
>> > on
>> > the
>> > type of user (manage or employee). But both switchboard calls on some
>> > of
>> > the
>> > same form; like my states form. This form has the buttons of Add,
>> > Update,
>> > Delete, and so on. The manager would have the right to do all of the
>> > functions but I want the employees to only have the right to just
>> > Update.
>> > So
>> > if an employee login and opening the states form I want the Add and
>> > Delete
>> > button to be disenable and if a manage login all the buttons stay
>> > enable.
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/11469-disenabling-buttons-base-on-user.html
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11469
>> > So I would like to know does anyone know how to design is code because
>> > I
>> > am
>> > having some problems designing it.
>> > Thank you,