Re: AW: Internal server error when viewing sample asp scripts

2003-09-12 Thread D. L. Fox
> I would think "Response.Write" would be a common one. If the VB programmer really cares, it starts with Option Explicit. Regardless of that, they need to use Dim. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional comm

Re: AW: Internal server error when viewing sample asp scripts

2003-09-12 Thread Richard Curtis
> >> However, I disagree with the premise that this will help the end user > >> confusion. Most initial posts on this subject are with an internal > >> server error resulting, as the developer has not yet set Debug 2 or 3 > >> which are the settings which will result in a verbose HTML message > >>

Re: AW: Internal server error when viewing sample asp scripts

2003-09-12 Thread Josh Chamas
Warren Young wrote: Josh Chamas wrote: However, I disagree with the premise that this will help the end user confusion. Most initial posts on this subject are with an internal server error resulting, as the developer has not yet set Debug 2 or 3 which are the settings which will result in a verbo

Re: AW: Internal server error when viewing sample asp scripts

2003-09-12 Thread Warren Young
Josh Chamas wrote: However, I disagree with the premise that this will help the end user confusion. Most initial posts on this subject are with an internal server error resulting, as the developer has not yet set Debug 2 or 3 which are the settings which will result in a verbose HTML message goin

Re: AW: Internal server error when viewing sample asp scripts

2003-09-12 Thread Josh Chamas
Warren Young wrote: Uwe Riehm wrote: Maybe for the time being a quick and dirty hack could be a solution to this: just search / match in the input file for some of the most used keywords of VBScript and in case one of those is found stop all the processing and output such an error message. A

Re: AW: Internal server error when viewing sample asp scripts

2003-09-12 Thread Warren Young
Uwe Riehm wrote: Maybe for the time being a quick and dirty hack could be a solution to this: just search / match in the input file for some of the most used keywords of VBScript and in case one of those is found stop all the processing and output such an error message. A refinement on the idea: