i dont think the problem is limited to win 2003 systems...
i am talking about kix32 scripts as published apps.
by this i mean launching the app via kix32.exe <scriptname> or wkix32.exe <scriptname> directly from the citrix server.
If you try to launch a 4.22 script directly as a published app, it will not stay running if the script enters a inactive state, like a get statment, or waiting on a kixforms event. You could get a 4.22 script working by launching it from a bat file that uses the command prompt. since the command prompt does not have this bug, the script stays running.
This was the problem that i was having here... and was thinking it was a kixforms problem.
