login

[Zahkay]

Hello 

I really need help concerning login in labview.

I wanted to make to seperate login where one is for admin and the other is for user.

can somebody help me please

[muks]

Search for reference

[Zahkay]

hello sir,

I check those vi you suggest me. But me my problem is i dont know how to implement it in my work,

i am using even structure sir

[muks]

Post a scrren shot and tell us where you are stuck

[Zahkay]

Sir this is the login i did and it is working perfectly fine

but it is a prompt user login

but me i dont want this.. i want to have a normal user login and admin login ( where can add to delete user).

[billko]

I don't understand.  The very definition of a login is a prompt that asks you to log in.

[edit]

Oh, I see.  You want an integrated login.

[/edit]

[billko]

So, once you have this integrated login, are you prepared for the task of enabling/disabling functions according to the security level?

[Zahkay]

Yes sir this is the one i wanted but i am having problem when i am trying to do it in event structure

[billko]

---

@Zahkay wrote:

Yes sir this is the one i wanted but i am having problem when i am trying to do it in event structure

---

Look into creating a Queued Message Handler.  There is a template shipping with later versions of LabVIEW.  You can also do a Google search.

Your first state would be something that disabled all the controls except for your login stuff.

Your next state would be triggered by a login event.  This state would contain your security stuff, and would simply enable the controls that the user is allowed to use (while disabling the controls they aren't allowed to use) based on the results of your security algorithm.

The rest of the states would simply respond to specific events on your fornt panel.  Remember, you don't need code to prevent unauthorized access to these controls because that's all taken care of by simply disabling that control above.  Remember, the exit button is one of these, and the state that responds to your exit button is where your cleanup code goes.

If running in dev mode, remember to make it so the user can't just open the VI and modify it to bypass the security.