Here's the flow:

LogIn Page(index.asp):
   Validate login from db then set db values to 
         Session variables. 
  IF okay, 
    set Session("StudentID") = rs("StudentID")
    Redirect to Schedule.asp

Schedule.asp:
    if Session("StudentID")="" then
       Redirect to index.asp
    else
       Display Schedule page with values from access db.
       if Student Chooses to update schedule, click on 
       Update Schedule button.
       Update Schedule:
           Call Screensurfer on same machine but different
           port (82) navigate through screens to schedule 
           screen. Write values access db then Redirect to 
           Schedule.asp
    End if

When I redirect to Schedule.asp, Session("StudentID") is checked if it exists. It doesn't exist. I did a res

Generally, this component is based on Visual Studio-generated code, and we haven't really done anything with session variables although we have the methods available to access them...but maybe if we say we're interested we NEED to do something.

Also, I don't think this component has been compiled under latest Service Pack to VStudio- so we will try to reproduce the session variable "whack", then see what we need to do to make it go away.

I took the "AspSurfer Test Page" (SurfTest.asp) and updated it so that looks like this around the call to SS:

<% Session("TestVar")="Hello" %>
<h2>TestVar="<%=Session("TestVar")%>"</h2>
<% Set SS = Server.CreateObject("SSurfer.AspRequest")
   SS.AddInput "Bozo","Hello there I'm Bozo!..." 
   SS.AddInput "Greta","That Bozo is such a cad, + 
               is like a 50% solution!"
   SS.AddInput "Poncy","500"
   SS.SurferAddress="localhost:82"
   SS.Execute "Surfer/Details" 
   SS.ShowAllRecordSets%>
<p>
<h2>TestVar="<%=Session("TestVar")%>"</h2>