It is the first time we read something about "users make their own scripts".
Indeed kix32 doesn't have an error recovery mechanism, but with our
tool kixstrip you can pre-process it and you can verify the kixtart
code.
At the moment kixstrip doesn't return an errorlevel, when it encoun-
ters an error situation. We put something on our TO-DO list with a high priority.

A way of running your script without an abortion created by another script
can be by using the run or shell command.
A possible structure:

code:

---

;
; -first part of your script-
;
IF (Exist("c:\user.kix") = 1)
   SHELL '%comspec% /c kix32 c:\user.kix'
ENDIF
;
; -next part of your script-
;

---

By using kixstrip we are also using find command and GetFileSize function:

code:

---

;
; -first part of your script-
;
IF (Exist("c:\user.kix") = 1)
   ; - kixstrip is located somewhere on the server f.e. netlogon directory -
   SHELL '%comspec% /c kixstrip c:\user.kix nul                       >%temp%\zzzzz1.tmp'
   SHELL '%comspec% /c find /n /i "no errors found" %temp%\zzzzz1.tmp >%temp%\zzzzz2.tmp'
   IF (GetFileSize("%temp%\zzzzz2.tmp") < 30) THEN
      CALL "c:\user.kix"
   ELSE
      ? "Warning KIX: script of user contains errors."
   ENDIF
   del "%temp%\zzzzz?.tmp"
ENDIF
;
; -next part of your script-
;

---

code:

---

---------- c:\users.kix
[11] Informative KIXSTRIP:   no errors found.

---

btw: check the differences between file sizes with and without errors in your situation.
btw: kixstrip can only handle 8.3 filename.