The basic idea is that you have a small form with a box for inputting username, a box for inputting password, and that you have a table in your database where you can check one against the other. The purpose of the MD5 hash is that it allows your passwords to be stored in the table in an encrypted fashion.
It's going to take some time and effort on your part to figure this out, but the basic components are there.
Thanks for that but maybe you didn't get me very well, i already have a login form that works perfectly but what i want is that since my application is going on a network of between 45-77 users, i need to be able to monitor users as they log in and log out, like a table that stores user who log in including the time of logging in and out
If you already have a login form, then all you need to do is create a table to store the details you want, and have the login form run an append query whenever the user logs in or out. The Now() function will probably come in handy for supplying the time stamp.
Like Pat said, it's going to take some time and effort on your part, but we can help with specific issues you run into.
If you already have a login form, then all you need to do is create a table to store the details you want, and have the login form run an append query whenever the user logs in or out. The Now() function will probably come in handy for supplying the time stamp.
Like Pat said, it's going to take some time and effort on your part, but we can help with specific issues you run into.
Thanks for that but maybe you didn't get me very well, i already have a login form that works perfectly but what i want is that since my application is going on a network of between 45-77 users, i need to be able to monitor users as they log in and log out, like a table that stores user who log in including the time of logging in and out
Well that is a much clearer explanation than your first post. Knowing all that, I would say that gershwyn's suggestion is a good way to go. Just set a table up that you do an INSERT INTO when someone logs in, and a DELETE when they log out.
The devil will be in the details though. In particular, I'm thinking of unusual circumstances like what happens when Access quits unexpectedly, or something like that.
Well that is a much clearer explanation than your first post. Knowing all that, I would say that gershwyn's suggestion is a good way to go. Just set a table up that you do an INSERT INTO when someone logs in, and a DELETE when they log out.
The devil will be in the details though. In particular, I'm thinking of unusual circumstances like what happens when Access quits unexpectedly, or something like that.
Comment