I can launch it fine either way (with the full path and filename in the 2nd parameter passed to createprocess and .null. as the first parameter or with the path and filename as the first parameter and the command line parameters as the 2nd parameter) but either way, it still fails once it is running. It doesn't seem to be able to grab its own path once it runs because once it is launched and running it fails after that and just hangs. Thanks for the information though it was useful for testing!

Tracy

>Have you tried launching cmd.exe instead of transman.exe? Nice for debugging things like this.
>
>Some programs are picky about getting a fully qualified name for argv[0] (first param of CreateProcess()). Some others dislike being started from paths containing blanks unless the executable name is quoted in a certain way, because their command line parsing code is broken. Such a program would think that it resides in a folder called "c:\program" or that "program" is its own name and the path is "c:\", when it is actually located in "c:\program files\what\ever".
>
>So you could try passing a fully qualified name as the first param for CreateProcess() but you could also pass .null. for the first parameter and build a complete command line (including the executable name) for the second parameter. Windows will do path searching for program names in the second parameter but not in the first, and it will probably supply the full path to the program even if you pass an unqualified name in the second parameter.
>
>E.g., assuming cmd.exe is in the path but not in the current directory, RunAndWait("cmd.exe") would fail but RunAndWait(.null., "cmd.exe") would not.