Dan,

You didn't answer my question how lcCommandline looks when it errors out. W/o that info I cannot see what could be wrong.
The GetLastError may help you to find a problem.

>GetLongPathName works great. Thanks.
>
>The following code errors:
>
>

>SET CLASSLIB TO PROCESS.VCX ADDITIVE
>lcParams = "c:\temp\test.txt"
>lcCommandline = "NOTEPAD.EXE " + lcParams
>oProcess = CREATEOBJECT('API_AppRun', lcCommandline, "", "NOR")
>oProcess.LaunchAppAndWait()
>

>
>The error w/in the class is:
>Process Specified by icCommandLine could not be started
>
>If I put the full path and remove the parameters it works fine.
>
>Once I add the parameters, I get the same error as above.
>
>I haven't looked into the GetLastError API call.
>Maybe I should check that.
>
>>>Maybe I have an older version of the class.
>>>
>>>The following fails:
>>>1. When I don't include the full path.
>>
>>Yes, you've to provide full path if program isn't located along Windows search path
>>
>>>2. If I put any parameter in the command line.
>>
>>What error do you get? Can you post your code and the command line with parameters you're trying to execute?
>>If path or parameters have spaces, they should be encloused in double quotes.
>>
>>
>>>I have another related question.
>>>Using the GetEnv( Temp ) we are getting the temp folder but it is
>>>geeked out w/"~" in the path.
>>>
>>>The API_APPRUN class will not run correctly using that path.
>>>How do I get to the full path?
>>
>>See Re: DOS paths vs. Windows paths Message #810026