Hey.  I asked a question a while ago and just want to say thanks.  The 
answer you gave was right on the money.

For that reason I am comingto you with another question:
I can't get any of my ASP code to display on my machine!  I did a few of 
the examples from your book (Beggining ASP 3.0) and they worked great (I 
did the "Time in Webserverland" and "InteractiveDirectory").

I've just started writing my own app.  Things were going fine at first.  
I wrote my register page, which used ASP to greate directories, write 
info to the dirs, and store info in Access.  

The problem came when you hit the submit button.  The browser was 
directed to a framed page.  All of the frames in this page were empty 
except two.  The two populated frames were ASP pages.  The first frame I 
populated worked fine.  When I went to insert the second ASP frame, 
however, things went all screwy.  

Once I had worked all the bugs out, I was greeted by a blank frame.  
Nothing but white background.  The other populated ASP frame was blank 
too!  The empty frames simply displayed the 404 error.  As iff this were 
hot wierd enough, now NONE of my ASP pages load.  The HTML sections load 
just fine, but all sections containing ASP are blank!  I have tried 
loading the pages from Windows Explorer, IE, and IIS.  All yield the same 
result.

What is going on!?!

P.S. Before I began getting "Phantom" ASP code I was getting errors 
saying that a page could not be displayed because too many users were 
trying to access it, but I was the only one.  I would close IE down, re-
open it, and get the same "Server too busy" error.  I would have to 
restart my machine.

a) You need to make sure that you are addressing the page correctly eg:

<frame src="/myFramePage.asp">

not

<frame src="c:\inetpub\wwwroot\myFramePage.asp">

because your webserver needs to process the ASP code. If you do it the
second way, then you are just loading a file off your hard disk, and the
webserver (and asp.dll) doesn't get a chance to process the ASP code. You
can check this by doing a "View Source" on your "phantom" page. If you can
see ASP code in the HTML source, then it's not being parsed by the
webserver.

b) If you have an infinite loop (eg you forget to use .movenext or similar),
then you page will never finish processing, and nothing will ever be
displayed. Your CPU utilisation will go to 100%, and you webserver will stop
responding to new requests. If this might be the case, post some code.

Cheers
Ken

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
----- Original Message -----
From: "Bryan Maynard" <Bryan_Maynard@m...>
To: "Access ASP" <access_asp@p...>
Sent: Tuesday, January 21, 2003 6:26 AM
Subject: [access_asp] Blank ASP pages!


: Hey.  I asked a question a while ago and just want to say thanks.  The
: answer you gave was right on the money.
:
: For that reason I am comingto you with another question:
: I can't get any of my ASP code to display on my machine!  I did a few of
: the examples from your book (Beggining ASP 3.0) and they worked great (I
: did the "Time in Webserverland" and "InteractiveDirectory").
:
: I've just started writing my own app.  Things were going fine at first.
: I wrote my register page, which used ASP to greate directories, write
: info to the dirs, and store info in Access.
:
: The problem came when you hit the submit button.  The browser was
: directed to a framed page.  All of the frames in this page were empty
: except two.  The two populated frames were ASP pages.  The first frame I
: populated worked fine.  When I went to insert the second ASP frame,
: however, things went all screwy.
:
: Once I had worked all the bugs out, I was greeted by a blank frame.
: Nothing but white background.  The other populated ASP frame was blank
: too!  The empty frames simply displayed the 404 error.  As iff this were
: hot wierd enough, now NONE of my ASP pages load.  The HTML sections load
: just fine, but all sections containing ASP are blank!  I have tried
: loading the pages from Windows Explorer, IE, and IIS.  All yield the same
: result.
:
: What is going on!?!
:
: P.S. Before I began getting "Phantom" ASP code I was getting errors
: saying that a page could not be displayed because too many users were
: trying to access it, but I was the only one.  I would close IE down, re-
: open it, and get the same "Server too busy" error.  I would have to
: restart my machine.