password from table

[hsl9999]

I would like each individual to have a username and password so that certain users can have access to certain menus and reports. I made a table called user that contains the following fields: userID, username, userpassword, usercategory. (The usercategory uses a simple lookup that includes administrator, back office, front office, salesman.) Now I would like to have the main menu that pops up when the program is loaded to have 2 entry fields" User Name and Password. If the person enters the correct combination then he/she is automatically sent to the real main menu. If the combination is incorrect then the user is given 3 chances to enter the correct combination and is then locked out for 10 minutes. Only the administrator can then unlock the program once a non-adminstrator is locked out or they can wait the 10 minutes to have 3 chances again. Once the user gains initial access he/she can only open certain forms or go to certain reports that are allowed by the users category. I hope that I have been explicit enough not to confuse the issue here. Thanks for any help.

[Raymond Lyons]

Re: password from table

While you certainly can roll your own, is there some reason you don't want to use Alpha's built-in security system, which I think pretty much does what you want? You might want to create a test database and try it out to see how it works (in the Control Panel, Tools, Security). I have both rolled my own and used Alpha's and though mine works, I kind of like Alpha's built-in system.

Raymond Lyons

[hsl9999]

Re: password from table

Yes, The alpha system is excellent, but I wanted to give each person 3 tries and then lock their entrance for 10 minutes unless an administrator unlocks them. This I did not see in the built in security system.

[Keith Hubert]

Re: password from table

Hi Harold,

but I wanted to give each person 3 tries and then lock their entrance for 10 minutes unless an administrator unlocks them.

The built in security does allow for a maximum number of tries. With regard to being locked out for a time, this seems to me to be a Catch 22 situation. How will the system know to lock out a user if they have not been recognized as a valid user in the first place?

[Mike Wilson]

Re: password from table

Keith,
I'm thinking when the user can't get the right password.

Harold,
What you are discussing id a login system. I have a system I have been using. I will post it as an example later when I get a chance.

[Raymond Lyons]

Re: password from table

Keith,
I'm thinking when the user can't get the right password.....

Yes, a roll your own security system could allow one to wait the 10 minutes or go see the administrator if the user can't get the password right but I don't see how this is enough of a plus over the A5 built-in system to justify going this route. Not saying there isn't something that would justify it, just that lacking imagination at the moment, I can't imagine what it would be.

I built my own system way back when Alpha Five did not have one built-in. It worked (and is still working) but since then I have used the A5 built-in system and prefer it. Also, though it may be a bit complicated, it is possible to add features to the built-in system, such as adding user data such as telephone extension, etc. to a table when the user is setup using the built-in security functions.

Raymond Lyons

[Mike Wilson]

Re: password from table

OK,
This is somewhat trimmed down, as I compiled it from another application. It has a login form and uses a login_sequence UDF (user defined function) operating off of a login form, looking into a Contacts table for the user name and password, drawing parameters from a systems variable table (sys_var) for the login attempts allowed and the time out period desired. It is not the most straight forward or succinct of scripts at 291 lines (I wrote it a while back) but handles the needs and does the job, and exemplifies what was claimed as desired.

Holler back if you need more help