Yogi,
Welcome to the board!
One of the things that KiXtart does do at the time of execution, it will try to tell you what the error is.
Another thing to think about is how you code. That is proper indenting. If you have an IF, you need a corresponding ENDIF. And the statements inside it should be nested to be easily spotted for structure.
Another way to do this is to get a copy of KiXStrip and run your script through it.
For example:
Code:
CLS
BREAK ON
IF EXIST('C:\BOOT.INI')
?'DOES EXIST'
GET $
And I get for a result:
Code:
CLS
BREAK ON
IF EXIST('C:\BOOT.INI')
?'DOES EXIST'
GET $
;($begin)
;
; thu 21-apr-2005 05:42:38 (kix 4.20 vs 4.00e)
;
;Informative KIXSTRIP: input=5 output=5 skip=0
;
;Warning KIXSTRIP: 1 error in block structure. missing statement(s).
; - do:until [0:0]
; - for|each:in|to:step|next [0|0:0|0:0|0]
; - function:endfunction [0:0]
; -ERROR- - if:else:endif [1:0:0]
; - select:case:endselect [0:0:0]
; - while:loop [0:0]
;Warning KIXSTRIP: some lines contains errors or possible errors.
;Informative KIXSTRIP: 1 block_structure found.
;Informative KIXSTRIP: no UDF's found.
;Informative KIXSTRIP: no labels found.
;Informative KIXSTRIP: 1 BREAK
;Informative KIXSTRIP: 1 GET
;
;($end)
;($begin)
;
;
HTH,
Kent
