Thanks,
Tommy

KiX has extensive error codes that are returned (@ERROR/@SERROR), to provide complex scripting possibilities when a condition does not return the 'expected' return value.

So, if your script is aborting, your script needs to be checked. Suggest obtaining the standard for KiX script checking programs created by MCA, kixstrip, available at http://home.wanadoo.nl/scripting

Bill

The problem I am having is when I instantiate a custom COM+ Server. If the correct registry keys for the COM object do not exist on the client, the script will terminate. I know I can check to make sure each of the keys/values exist in the registry before instantiating the COM object, but that seams excessive to me. I would like the script to continue if it can’t run the COM object.

Any suggestions appreciated.

Thanks,
Tommy

You can check for successfull object creation like this. This example tries to create script.filesystemobject.22, which doesn't exist ...

break on

$object = createobject("scripting.filesystemobject.22")

if not $object
 ?"Error instantiating object. taking appropriate steps ..."
else
 ?"All is well with wsh ..."
endif

exit 1

My assumption here is that failure to instantiate a COM+ object (for whatever reason) will still return back a NULL (not) pointer.

-Shawn

At this moment nothing with capability is available in KiXtart language.
On the suggestion forum you can find all kind of new wishes.
Shawns reaction is only for specific location in your script. Sometime
necessary to prevent unexpected results.
greetings.

Thanks,
Tommy