Home arrow ASP arrow Adding Member Services in ASP

Adding Member Services in ASP

What to add member services to your site? James will explain how this is done using ASP so that your members can obtain different privileges.

Author Info:
By: James Shaw
Rating: 5 stars5 stars5 stars5 stars5 stars / 54
May 09, 2003

print this article

What to add member services to your site? James will explain how this is done using ASP so that your members can obtain different privileges.

Implementing a membership system for CoverYourASP was simple in concept, but ended up touching a lot of pages, and created 10 new ones!

Here's what I wanted, and got, from my system - I'll go through each one in the following pages:

  • Members can register themselves via a form.
  • Validation of membership changes via email.
  • Sign in/out using users email address and password.
  • Option to sign in automatically using a cookie (low security).
  • Ability to send password to members who forget.
  • Multiple levels of membership with more functionality.
  • Free Bronze membership has database storage of site personalization.
  • Easy upgrade to higher membership level using PayPal.
  • Members-only area available only to Silver members.
  • Registering new members
  • Registering a new user requires a straightforward form that adds a new record to the database.

You can view the real source code here, but before you do, I should tell you that the same form is also used to edit existing member information too.

A simple call to IsLoggedIn ( ) - a function defined in the utils/Login.asp file - allows me to tell which task I'm undertaking with the form. It also controls what action I'm taking in the database, as the excerpt below shows:

// connect to the database
DBInitConnection ( );
if ( IsLoggedIn ( ) )
   // update the member information
   oConnection.Execute ( 'UPDATE Members SET Name=\'' + sName + '\',Email=\'' + sEmail + '\',MemberPassword=\'' + sPassword1 + '\' WHERE MemberID=' + nMemberID );
   // create the new member record
   oConnection.Execute ( 'INSERT INTO Members (Name,Email,MemberPassword) VALUES ("' + sName + '","' + sEmail + '","' + sPassword1 + '");' );
// release the database
DBReleaseConnection ( );

Having added the new member to the database, there is one more step the user must take before he can sign in...

Email Validation of Membership Changes

I wanted to validate the creation and deletion of members via email, and I wanted it to be automatic. A simple email to me wasn't good enough, but I didn't want to develop an application that listened to email coming in either.

I compromised by sending the member an email that contained a link to a new confirm page, named C.asp. The user has to click on the link (if their email client supports that), or cut/paste the link into their browser.

The email I send to confirm a new user was created with this code:

// send Email with our generic function
var sBody = 'Dear ' + sName + '\n\n';
sBody += 'To complete the registration of your CoverYourASP membership account please click on the link below, or copy and paste the entire URL into your browser.\n\n';
sBody += 'http://CoverYourASP.com/C.asp?a=a&e=' + sEmail + '&i=' + nID + '\n\n';
sBody += 'Regards,\n';
sBody +=
sBody += 'http://CoverYourASP.com/';
SendEmail ( 'MemberServices@'
+ sHostDomain, sEmail, '', 'New membership', sBody );

This generates an email that contains this line:


(Note: Many email clients will suffer from a "wrap" problem, meaning the hyperlink they show will only include the part of the URL on the first line. In this case the user must use the cut/paste method to use the entire URL)

C.asp in turn has the following code to decode that URL and perform the task of setting the Confirmed flag in the member record.

var sAction = '' + Request.QueryString ( 'a' );
var sEmail = '' + Request.QueryString ( 'e' );
var nID = Request.QueryString ( 'i' ) - 0;
switch ( sAction )
case 'a':
   DBInitConnection ( );
   // set the confirmed status on the membership
   oConnection.Execute ( 'UPDATE Members SET Confirmed=1 WHERE MemberID=' + nID + ' AND Email="' + sEmail + '"' );
   DBReleaseConnection ( );

One last note - C.asp doesn't bother reporting if the parameters given were invalid. If the Email doesn't match the given ID then the database won't be modified thanks to the SQL statement used.

Signing In and Out

The sign in process starts with a call to ShowLoginStatus( ) in utils/Header.asp. The ShowLoginStatus function contains the following code:

if ( IsLoggedIn ( ) )
   Out ( '<a href="MemberLogout.asp">Sign out</a> ' + sMemberName );
   Out ( 'Join in the fun! <a href="MemberLogin.asp">Sign in</a>' );

This will be the first call to IsLoggedIn( ), which first checks if the function has already been called on this page (if bLoggedIn is undefined), then checks if the Session has been signed in.

Every visitor gets assigned a unique session - Session variables like this are available to every page on your web site, and allow you to store data that is unique to each visitor.

If signed in then some other global variables are assigned from the current Session - this just makes it less expensive to access this data later in the page.

if ( bLoggedIn == undefined )
    bLoggedIn = Session ( 'Authenticated' );
   if ( bLoggedIn )
      sMemberName = Session ( 'MemberName' );
      sMemberEmail = Session ( 'MemberEmail' );
      nMemberID = Session ( 'MemberID' );
      nMemberLevel = Session ( 'MemberLevel' );
return bLoggedIn;

Back in ShowLoginStatus( ), the user is either shown an option to sign in, or sign out. Signing in is done with a simple form asking for the member email and password. The ValidateLogin( ) function is then called when the form is submitted. Let's look at the ValidateLogin( ) function:

// connect to database
DBInitConnection ( );
// search for matching email/password
DBGetRecords ( 'SELECT MemberID,Name,MemberLevel FROM Members WHERE Confirmed=True AND Email=\''+sEmail+ '\' AND MemberPassword=\'' +sPassword+ '\'' );
if ( !oRecordSet.EOF )
   Session ( 'MemberEmail' ) = sEmail;
   Session ( 'MemberID' ) = oRecordSet ( 0 ) - 0;
   Session ( 'MemberName' ) = '' + oRecordSet ( 1 );
   Session ( 'MemberLevel' ) = oRecordSet ( 2 ) - 0;
   Session ( 'Authenticated' ) = 1;
// release database
DBReleaseConnection ( );

So the database is searched for a matching email/password. If found the Session variables are initialized to the correct values, and the visitor is "signed in"!

Signing a member out is a little easier! A call to Logout( ) in utils/Login.asp contains this code:

// clear the authenticated status
Session ( 'Authenticated' ) = 0;

Big Important Note: Before I leave the subject of signing in, you should be aware that my implementation is NOT SECURE. Password information over a normal HTTP connection can be seen by anyone. On my site this isn't important, but remember to send important information via HTTPS in real life.

Forgotten Passwords

Sending passwords via email was very simple, although, yet again, a little unsecure. A form asks for the members email address, looks that up in the database and emails the password.
Here's the "essence" of the code that does all that:

DBInitConnection ( );
DBGetRecords ( 'SELECT Name,MemberPassword FROM Members WHERE Email=\'' + sEmail + '\'' );
if ( !oRecordSet.EOF )
   // get data from recordset
   sName = '' + oRecordSet ( 0 );
   sPassword = '' + oRecordSet ( 1 );
   var sBody = 'Dear ' + sName + '\n\n';
   sBody += 'Your password is: ' + sPassword+ '\n\n';
   sBody += 'Regards,\n';
   sBody +=
   // send Email with our generic function
   SendEmail (
+ sHostDomain, sEmail, '', 'Lost Password', sBody );
// release the database connection ASAP
DBReleaseConnection ( );
Creating levels of membership was trivial - I just added a new field to my table called... no, I should make you guess!
Another Session variable and global variable and I can now write code to test against membership level:

// are they a high enough level?
if ( nMemberLevel < nLevel )
   // no, let them know
   Out ( 'You need to upgrade your membership to ' + sLevels [ nLevel - 1] + ' - you are a ' + sLevels [ nMemberLevel - 1 ] + ' member.' );
   // valuable content goes here!

Free Site Personalization

Through a simple form you can change settings that control how the front page is displayed.

The only fun part of this was that I had to calculate how many books and banners to display down the side of a page - you can basically turn everything off! Here's the code I used:

// I have to calculate how many banners now
var nBanners = 1;
if ( bIntro )
if ( bSuggestions )
if ( bDiary )
if ( nNew || nPopular )
   nBanners +=  Math.floor ( (nNew + nPopular) / 2.5 );
if ( bCategories )
   nBanners += 3;
if ( bNews )
// show rotating banners
ShowBanners ( nBanners?nBanners:1 );

Currently you can hide/show the introductory text at the top, the categories and ASPWire news. You can also specify the number of articles in the New and Most Popular sections. Set to zero, and those sections disappear too!

Further plans? You tell me what you want, but I suspect that using my Yahoo-style category layout may be an option. It seems like I nearly have enough content to justify it!

Upgrade Membership

Ugrading membership, and how I used PayPal to accept payment are the subject of a separate article, to be published soon.

Members-only Area

Providing a members-only area required very little code. First I created a function in Login.asp:

// ============================================
// make sure the user is signed in, and has sufficient access rights
// if not then redirect to passed in page
// ============================================
function NeedAccessLevel ( nLevel, sRedirect )
   if ( !IsLoggedIn ( ) )
      Redirect ( 'MemberLogin.asp' );
   if ( nMemberLevel < nLevel )
      Redirect ( sRedirect );

The function takes two parameters - the level required and a page to redirect to if the members level is lower than necessary.

Here's how I use it in the exclusive member-only pages - add this code to the top of the page, before the call to Init(), in case the function redirects the user:

// need signed in members of level 2 and above
NeedAccessLevel ( 2, 'MemberUpgrade.asp' );

DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.

All ASP Tutorials
More By James Shaw

blog comments powered by Disqus

- Central Scoreboard with Flash and ASP
- Calorie Counter Using WAP and ASP
- Creating PGP-Encrypted E-Mails Using ASP
- Be My Guest in ASP
- Session Replacement in ASP
- Securing ASP Data Access Credentials Using t...
- The Not So Ordinary Address Book
- Adding and Displaying Data Easily via ASP an...
- Sending Email From a Form in ASP
- Adding Member Services in ASP
- Removing Unconfirmed Members
- Trapping HTTP 500.100 - Internal Server Error
- So Many Rows, So Little Time! - Case Study
- XDO: An XML Engine Class for Classic ASP
- Credit Card Fraud Prevention Using ASP and C...

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 

Developer Shed Affiliates


© 2003-2019 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials