Home > Articles > Programming > Visual Basic

  • Print
  • + Share This
Like this article? We recommend

Identifying the User

As I wrote in my previous article, identifying a user involves generating some kind of unique identifier and then including this identifier on each request from the user to the application running on the server. A unique identifier can be generated using any number of algorithms. It could be based on a random number, the current date and time, a Globally Unique Identifier (GUID), a UserID if the user is required to log on to your application, a record ID if you store state information in a relational database, or any combination of these.

To keep my sample code as simple as possible for example purposes, it generates a unique identifier using the server's current date and time, and then appends it with a five-digit random number. This value serves the same purpose as the ASP Session SessionID, but I'll refer to it as the UserID so as not to confuse the two. Theoretically, my algorithm could generate a UserID already in use, and so perhaps it should include code to check to see if a state file with this identifier already exists. If so, it could continue generating numbers until a unique value is found.

An even more robust approach is to use a Globally Unique Identifier (GUID) for the UserID. A GUID is a large, statistically unique, 128-bit number generated from the address of the Ethernet card in the current machine, the current time, and I think some voodoo magic. The GUID-generating algorithm should never produce duplicate numbers because it is capable of creating 10 million numbers unique to your computer's network card every second for almost 4,000 years. See Article ID Q176790 on the Microsoft Web site for sample Visual Basic code that can be used to generate a GUID.

Begin coding by opening the PublishersWebUI project created in the "Develop Scriptless Web Apps Using Visual Basic" article. Add a class module to the project, set its Name property to clsUserState, and set its Instancing property to 1 – Private. Open the class module's code window, and add the following to implement the UserID property:

Private mUserID As String

Public Property Get UserID() As String
  UserID = mUserID
End Property
Public Property Let UserID(ByVal lUserID As String)
  mUserID = lUserID
  ' Generate a new UserID if none exists.
  If mUserID = "" Then
    mUserID = Format(Now, "yyyymmddHhNnSs") & Format(Rnd * 99999, "00000")
  End If
End Property

UserID is exposed from the class by using Property Procedures so that when the UserID property is set, a new value can be generated if an empty string is passed. We should expect this to happen only when a user first makes a request to the application.

Now that we have a way to generate a unique identifier, we need to modify the other parts of the code so that this value is always passed back and forth between the browser client and our application running on the server. I like to pass this value as a URL query string parameter. This requires that it be included on all hyperlinks in our application's HMTL code. Because the UserID value cannot be determined when the HTML code is created, our application must dynamically modify all HTML sent to the browser that includes a link back into this same application to include this user's UserID. This is known as "URL rewriting" by Java Server Page (JSP) developers.

One easy way to do this is to include a placeholder "token" for the UserID when authoring the HTML hyperlinks. For example, the search form for this sample application posts the form's contents back to the application. So it must be modified to include the following with the uid (UserID) token:

<form method="POST" action="PubWebUI.asp?uid={uid}&action=SearchProc">

All HTML (either from HTML files or generated by the application) that link back into our application need to contain this token. If even one link is missed, the user's state information will be lost when the user links to that page.

The next step is to modify the application code to replace the {uid} token with the actual value just before any HTML is sent. Recall that the sample application sends all user requests through a single WebMain method. To minimize the chances that HTML will be sent without the token being replaced, we can alter the code so that the only place an HTML string is sent back to the browser is at the end of the WebMain procedure. All other procedures simply populate a module scope string variable (for example, mHTMLSendString) with the HTML they want sent. The WebMain procedure handles changing the uid token to the actual value just before sending mHTMLSendString to the browser.

Again, taking advantage of the fact that all requests pass through the WebMain procedure, we can alter WebMain to attempt to retrieve the uid value from the query string and hand it back to the clsUserState object. Remember that the clsUserState.UserID is coded as a property procedure, and that is we attempt to set the UserID property value to an empty string, it will assume this is the first request for the user and generate a new UserID value. The centralized WebMain procedure is also a great place to restore state information as soon as the user's request is received, and to save it once the user's request has been processed.

Here's how the sample application's WebMain procedure looks with the previously mentioned modifications in bold type:

Private mHTMLSendString As String    ' The HTML that is sent back to the browser.
Private mUserState   As clsUserState ' The state information for one user.

Public Sub WebMain()
  On Error GoTo ErrHandler
  ' Try to restore this user's state information.
  Set mUserState = New clsUserState
  mUserState.UserID = gAspReq.QueryString("uid")
  Call mUserState.GetState
  Select Case gAspReq.QueryString("action")
    Case "SearchSend"
      Call SearchSend
    Case "SearchProc"
      Call SearchProc
    Case "DetailProc"
      Call DetailProc
    Case Else ' Otherwise send a default page.
      Call SearchSend
  End Select
  ' Rewrite any URLs in the HTML string to include the User ID.
  mHTMLSendString = Replace(mHTMLSendString, "{uid}", mUserState.UserID)
  Call gAspResp.Write(mHTMLSendString)
  ' Save this user's state information.
  Call mUserState.SaveState
  Exit Sub
  Call gAspResp.Write(Err.Description)
End Sub

Note that the GetState and SaveState methods for clsUserState are discussed as follows.

In the previous version of this sample code, each sub procedure was responsible for calling gAspResp.Write to send the HTML string. In this version, instead of calling gAspResp.Write, these procedures must be changed to instead put the HTML to be sent into the module scope mHTMLSendString variable so that it can be sent by WebMain. For example:

Private Sub SearchSend()
  Dim lHTML As String
  lHTML = LoadHTML("Search.htm")
  lHTML = Replace(lHTML, "{Filter}", mUserState.Filter)
  lHTML = Replace(lHTML, "{PublishersTable}", "")
  HTMLSendString = lHTML ' Instead of Call gAspResponse.Write(lHTML) 
End Sub
  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020