Hello Steve,

This workstation is the only Win2000 PC that shows CMD windows regardless of hidden state...
The user has just moved to another department, so it's not an issue anymore, that is, until whomever takes over the position and works on that PC arrives, then it will be a priority again I'm sure...

The windows based FTP that I observed, had the lack of freedom to be un-monitored (WINZIP) OR fully monitored (BZ-ZIP or whatever).
With the old timey technique of sending via DOS prompt and re-directing output to a test file I am allowed to take corrective action when, say the connection is not made or a JES job is not found (err-reporting).

I'm still open to suggestion...
I have heard that macro-substitution was faster, I have code either way - but I can't clock the difference.


>Hmmm...does changing the 2nd parameter to 2 or 3 behave properly (meaning, minimized and maximized) on that machine? I know that's not what you want :) Is the machine in question the only Win2000 box, or does it work properly on the other Win2000 boxes?
>
>BTW, there is no need to use macro expansion, see below.
>
>Have you looked for a free windows based FTP control?
>
>>>What line of VFP code cause the cmd window to show?
>>
>>At every loFTP.run ---
>>
>>

>>   cFTPrun="FTP -s:ftpjcl >c:\aoef\TEST.FTP"
>>   loFTP=CreateObject("Wscript.Shell")
>    loFTP.run("command /c " + cFTPrun,0,1)    && concatenate the strings
>>   loFTP=NULL
>