There are two things here.

First, KiXtart needs to read through the entire script to parse it - until it does it won't know where to find the label that you want to jump to

Note, it is not executing the script at this stage, just reading it in and parsing it into a form that it can run it in later.

The second thing is the extra quote (") character. The problem with this tricky devil is that KiXtart does not treat an end of line as anything special. For instance:

code:
$sString="This is a multi-line
string that has carriage returns
embedded in it"

This is perfectly valid, and creates a string with carriage returns in. This is also valid:
code:
Function udfDemoFunction(
      $iParameter1,
      $iParameter2,
      Optional $sParameter3)
...

What happens in your case is that after the extra " character eveything you think is enclosed in quotes isn't, and everything that you think isn't, is. Got that?

Ok, in the following simple example the text in italics is considered to be within quotes. The text in bold is considered to be script code.

Break on CLS
"Display Some Text"" ?
$sVariable="Assign Text"
if @USERID="rhowarth"
"Hi Rich" ?
EndIf

As you can see, KiXtart will try to execute "Assign Text", "rhowarth" and "Hi Rich" as script commands and will error.

[ 05 March 2002: Message edited by: Richard Howarth ]