I am beating my head against the wall on where my error is. Can someone else please look at my code and tell me what is wrong? Thank you for the help!

<%
Dim Connection
Dim DSN
Dim Recordset
Dim SQL

DSN ="DSN=access_speakers"

SQL = "SELECT Subjects,Presentations FROM Speakers"

Set Connection = Server.CreateObject("ADODB.Connection")
Set Recordset = Server.CreateObject("ADODB.Recordset")

connection.Open DSN

Recordset.Open SQL,Connection

If Recordset.Eof Then
response.write "There are no records."
Else

Do While NOT Recordset.Eof
Response.write Recordset("Subjects")
Response.write Recordset("Presentations")
Recordset.MoveNext
Loop
End If

Recordset.Close
Set Recordset = Nothing
Connection.Close
Set Connection = Nothing
%>

What error are you receiving, exactly? I don't see anything in the code on the surface that would generate an error.

Yeah, me neither. I'd guess if you have a saved ODBC connection as a DSN, your web server doesn't have rights to it.

But I'd also change this code:

If Recordset.Eof Then
response.write "There are no records."
Else

Do While NOT Recordset.Eof
Response.write Recordset("Subjects")
Response.write Recordset("Presentations")
Recordset.MoveNext
Loop
End If

To

While NOT Recordset.Eof
Response.write Recordset("Subjects")
Response.write Recordset("Presentations")
Recordset.MoveNext
Loop

You could put an increment in there ( i = i + 1 ) and know if no records got returned. But that simplifies things a little bit and makes it easier to maintain smaller code, without breaking things. A do loop gets executed always, no matter what, and after one iteration, then it checks the looping condition. A while loop checks before the first run, so if you're already at the EOF, it won't execute the code in the loop.

The error is when it tries to return a page. It does not seem to find the database and says:"The page can not be displayed" So then I get no page showing my results.

It is a HTTP 500 Internal Server error.

I know it is something simple so thank you for the feedback and that was a nice tip on the code change.

Here's another code change, but this one is temporary, and you want to turn it off afterwards.

response.write("Opening database<br />")
connection.Open DSN
response.write("Opening recordset<br />")
Recordset.Open SQL,Connection
response.write("Reading data<br />")

I think you get the point. Since I don't know how to run asp code in debug mode and set breakpoints, don't even know if that's possible ( go .net ! ), some trace code will let you know how far it got before dieing.

Also, my asp is super rusty, but try adding making the first line

on error resume next

or

on error goto errorHappened:

and then however you catch it, response.write the err message. You'll need to play around like I said, because I stopped using vb script years ago and don't remember exactly all the syntax. But that should get you closer to the solution.

Is it an Access or SQL database? You might try using a connection string instead of a DSN. You can put that in an include file so you don't have a lot to manage, but that clears NTFS permissions.

It is connecting to an Access database.

I thought so. Are you running winserv03? What user is IIS running under? Probably ASP_NET or ASP_WP, I don't remember off hand, and I'm at the SQL workstation right now. Anyway, the first thing to make sure is that whatever user your asp code is running under has permission to the mdb file, and to the folder it's in (because it will have to create, manage, and delete the associated ldb file).

Might not be NTFS, but that's the type of thing where your query works when you do it by hand, and fails when you do it by code.

It appears that you're using Internet Explorer, so the good news is that there's a way to see the exact error message.

Go to Tools-->Internet Options-->Advanced, and uncheck the box that says "Show Friendly HTTP Error Messages". Reload your page and you'll see your error message (and more importantly, the line that it's on.)

My hunch is that John's right and that it's a connection issue, although I think the if-else logic should be left in (since it will return a 0 results message in the event that there are 0 results.) Sorry John...I gotta disagree with you at least once a year!

You guys are awesome and helped out a bunch. I ended up scrapping the DSN and just did a Connection String and it works.

Thank you so much!

Originally Posted by ADAM Web Design

My hunch is that John's right and that it's a connection issue, although I think the if-else logic should be left in (since it will return a 0 results message in the event that there are 0 results.) Sorry John...I gotta disagree with you at least once a year!

Relevant link exchange forum for three days? Lucky thing my wife wants a romantic weekend getaway!

I'll see your disagreement, and raise a point: The if/then/else logic tests the same condition as the loop code. Both of them check RecordSet.EOF, so you'd get the same answer, but also, an empty (zero row) recordset is a valid answer (Select * From Table Where 1=2) and a different thing from an error raised by a bad query. Or maybe you're saying I should have extended the code change sample to put a message after the while loop that says if the increment field (i = i + 1, and for the record do you realize how **** hard that is to type when I'm used to i++;) is zero, print a "No records found." message? In that case, you're right.