Can someone explain the mechanics of this error message to me?


application ended without sending a Web page back to the browser and without w3ClosingPage set to a Web page

Well, without ever having USED FlashConnect I can only guess that the
message is saying that you have sent a message back to the D3 server,
and it sent NOTHING back to the web browser.

You must have done “something� in the browser to initiate an action
…. Information would have been sent to the web server, then to D3,
and then …..

Normally there would be SOME kind of a response coming back to the
browser as the result of clicking a (submit?) button or whatever … if
you don’t send something back, the browser is waiting for a response
and will eventually get a timeout error.

If you DON’T want to send back a page that prompts for more data,
I’m guessing you call the w3ClosingPage routine, and pass it the name
of a page that displays something like “thanks for visiting� – if
the user wants to do something else they click on a button on this
page, or enter a new URL on the address bar.

Alternatively you can probably send HTML back to the browser.

Now it could be that you actually THOUGHT you were sending information
back, but your program bombed out ïƒ* FlashConnect may have some error
logs for this, otherwise you can use LIST-RUNTIME-ERRORS from TCL
(which is often an ‘educational experience’ :-)

HTH – and if not, remember we provide an alternative WITHOUT cryptic
message, or even the need to understand all of this HTML stuff (though
a little knowledge can be a good thing)


Ross Ferris
Stamina Software
Visage - the Visual Information System Application Generation
Environment
(just in case people were wondering about the acronym and were afraid
to ask - though we have more answers on the web site - you can even
find out about the Stamina acronym)

"Ross Ferris" <rossf (AT) stamina (DOT) com.au> wrote:
(Geez) And from someone who actually uses the software and isn't
trying to sell you something else...

The error means you executed a RETURN statement without executing the
standard sequence to generate a web page:
call w3htmlinit(...)
call w3htmlheader(...)
generate page data here...
call w3htmlfooter(...)

The error usually occurs in logic like this:
open file else return
or
read rec from file,id else stop
You have to remember that the end-user ALWAYS gets a return page, even
if it's an error page. My standard way to handle those errors is like
this:
open file else
call weberror(123)
return
end
or
read rec from file,id else
ErrorDesc = file:" ":id
call weberror(124)
return
end
My weberror program has a large Case structure that checks for known
error numbers and returns and appropriate message using the
FlashCONNECT Calls indicated above. Again, the end-user ALWAYS gets a
return page, even if weberror itself gets an error.

HTH,
Tony