...not sure why. new to .net, read most of wrox beginning asp.net w/ vb.net. too much stuff is unexplained.

here's my code. i believe that the the problem exists in the catch section, just after i assign a value to Sesion("Email"). all other Session variables are not set, except Session("Error"), which informs me of the catch.:

<%@ Page Language="VB" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.Oledb" %>
<%
Dim strCon as String = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source = " & _
  "D:\Inetpub\wwwroot\Network.mdb;"

Dim sql as String = "SELECT pwdPassword FROM tblPasswords WHERE memEmail='" & _
  LCase(Trim(Request("txtLogEmail"))) & "';"

Dim con as New OledbConnection( strCon )

con.Open()

Try
    Dim cmd as New OledbCommand( sql, con )

    Dim rdr as OledbDataReader
    rdr = cmd.ExecuteReader()

    If rdr.Read()=False Then
         Session("Error") = "Email address not registered."
    elseif rdr("pwdPassword") <> Trim(Request("txtLogPassword")) then
          Session("Error") = "Password incorrect."
    Else
     Session("Email") = LCase(Trim(Request("txtLogEmail")))
     rdr.Close()

     sql = "SELECT * FROM tblMembers WHERE memEmail='" & session("Email") & "';"

     Dim cmd2 as New OledbCommand( sql, con )
     Dim rdr2 = cmd2.ExecuteReader()
             Session("Name") = rdr2("memName")
            Session("Alias") = rdr2("memAlias")
            Session("MI") = rdr2("memMI")
            Session("Surname") = rdr2("memSurname")
            Session("Address") = rdr2("memAddress")
            Session("City") = rdr2("memCity")
            Session("AC") = rdr2("memAC")
            Session("Telephone") = rdr2("memTelephone")
            Session("URL") = rdr2("memURL")
            Session("Width")= rdr2("memWidth")
            Session("Blurbs") = rdr2("memBlurbs")
        rdr2.Close()
    End if
Catch
    Session("Error") = "TROUBLE! :("
End Try
con.Close()
sql = ""
Response.Redirect( "index.aspx" )
%>

Hi there,

I think the problem is in the Try part. If the Session("Error") gets set, it means that somewhere in the Try block an error is thrown.

Two ways to find out:

1. Debug. Step line by line through the Try block
2. Comment out the Try Catch construct temporarily, and see where the code crashes.

Maybe the SELECT statement does not return a record or generates an error.....

HtH

Imar


---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

you are correct; that's the whole point of a try block - to catch errors and deal with them.

i believe that the problem lies in the data objects, specifically the dataReader object. i suspect that it is because the dataReader, unlike the ADO recordset object, does not point to the first record when it is instantiated, but to BOF. additionally, i am not yet familiar with the java-like structure of .net, and its documentation.

it appears that the authors of this object intended that the user traverse the records by using a loop. in my case i have need for but a single field, and figure it useless to deploy a looping structure when it is hardly necessary. i recently discovered that the Read function traverses the records within the dataReader object.

this is not one of the better books that i have purchased, and i would not recommend beginning asp.net with vb.net to anyone who needs to understand the architecture. it is simply insufficiently thorough.

Try Catch blocks are designed to catch errors at runtime. At design time they can be a pain sometimes as you don't always now what error you're dealing with. So, either you'll need to run the code in debug mode, so you can examine the error in the Catch block, or don't use Try / Catch temporarily and see what error occurs.

When dealing with a single record in a DataReader, simply use its Read method in an If statement:

HtH

Imar

---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

thx. it's fixed now. still, it has been a long while since i touched anything java, and migrating to .net will take more than a refresher. thk microsoft for sdk documentation, where i found that which resolved my problems thus far.

thx for responding....