After receiving a few queries about how to store passwords using ACCESS and ASP, and then use them as "logins", I thought, well, why not write in a separate article, instead of attaching multiple ASP files that are full of confusing comments and variables only to be decipherable by my brain?I'm assuming you've installed, and are running PWS (Personal Web Server) on your machine, if you are not already working on a server that supports ASP.
First of all, create a database, for instance, customers.Define a table with all
fields you require (include email and password).
After
database has been created, you need to create a DNS in order to access this database through your ASP pages.
If you have never created it, this is how you do it:
Go to
Control Panel (My Computer -> Control Panel), and click on
icon that should be saying "ODBC Data Sources (32bit)". In
resulting window, select
"System DSN" tab. Then click on
"Add..." button. From
given list of Database drivers, select "Microsoft Access Driver (*.mdb)" and click
"Finish" button. You reach a place where you have to enter
"Data Source Name". Enter it, anything, for instance, "customers". Then click
"Select..." button. This lets you select
Access database you created. Press Ok, press Ok, and press Ok. Your DSN is created.
In
first part, I'll write about storing
passwords.
Before this, let's make an include file to create and initialize
session variables that we are going to need (we can use cookies, but some clever folks disable cookies on their browsers).
File name: sessions.inc
<%
if session("email")="" then session("email")="notlogged" session("pass")="" end if
%>
This file you can include in every page as
so that you can use them whenever you need them.
Now accepting login and password.
For this you require a normal HTML form. You can have "n" number of fields in a form, but here, our primary concern is, getting
email as login, and
accompanying password.
Here's
form:
Please enter your details:
We validate
form before it proceeds to
"action" file so that there is very little server-side processing. A simple validation:
Note: Put
following Javascript above
tag.So now when
user clicks on "Submit", he/she goes to "storelog.asp" In between, you can have a file to confirm
form fields and give
user an option to modify them before finally saving.