I issue the command
call cleanup.kix
from the main kix script but all I get is
Script error : Error in expression. !

I've also tried the following
call "cleanup.kix"
call \\servername\netlogon\cleanup.kix
call "\\servername\netlogon\cleanup.kix"
call %0\..\cleanup.kix
call "%0\..\cleanup.kix"

What is it I'm missing here?

Thanks.

call "[path] Scriptname"

and seems to be correctly used in your case ...

To get closer to a fix I recommend using MCAs kixstrip utility here

_________________________

Try using somthing like this

Call ("@ScriptDir\Outlook.kix")

I have not looked at what @ScriptDir is but I assume it is your netlogon directory.

Bye

Darren

dl the exe that fits your version 3.6x or 4.x,
the best results i got by copying the script in question to the folder kixstrip resides, open a DoS box cd to the dir kixstrip resides and type something like :
kixstrip400 yourscript.kix outputfile.ext /debug

hth

J.

_________________________

In this example, the call drive is the server netlogon share.

I use this so if changing directories to call KiX scripts from (primarily during testing), only 1 place in my script to change versus every CALL command.

This code is for KiX 3.63.

Bill

code:

---

Batch process to set variable:
SET TmpKixVar=1
%WinDir%\Kix32.exe %0\..\login.kix
SET TmpKixVar=
EXIT

KiX script to use variable and set CALL dir:
  SELECT									; REM **  Variable set/removed from batch file 'login.bat'
    CASE (%TmpKixVar% = 1) AND (@INWIN = 1)	$CallDrv = (SUBSTR (@LDRIVE, 1, LEN (@LDRIVE)-1))	; REM **  Removes trailing '\'.
    CASE (%TmpKixVar% = 1)			$CallDrv = @LDRIVE
    CASE (1)			$CallDrv = @CURDIR					; REM **  Script started from command prompt
  ENDSELECT
  ; REM **  Set where all scripts are called from (REGULAR or TEST directories)
  $CallKix = "$CallDrv\Regular"

Using CALL command within script:
CALL "$CallKix\kixscript.kix"

---

[ 25 January 2002: Message edited by: bleonard ]

Kixstrip has a lot of possibilities.

Simple calling: kixstrip
returns date and time information.

Calling: kixstrip ?
returns help information.

Calling: kixstrip input.kix output.kix /block_check
will verify your kixtart code.

Calling: kixstrip input.kix output.kix /debug
will insert additional debugging code to your script which will show
- which lines were executed.
- what was the time of execution.
- what was the error status of previous line.

Calling: kixstrip input.kix output.kix /performance
shows which part of your script consumes most of your time.

For additional information see our site:
symbol on our homepage has been linked to related http://kixtart.org topic.

greetings.

btw: the message "script error: in expression!" has nothing to do with your call.
you will not get an error even when specified script doesn't exist.
also the message should be something like "script error: unknown command.".

btw: a way to find your problem during execution is using our kixstrip
tool with the option /DEBUG. during execution it will show you exactly what
the last line of execution was.

btw: can you put your code on the board or send us a copy of it.