>>>>Nick,
>>>>It's very long and has a lot of command line switches,options and variables.
>>>>********************
>>>>lcCommand = gs_PSSQRBin+'SQRW.EXE' + " "+;
>>>> gs_PSSQRSrc+tcSQRName+'.SQR' + " "+;
>>>> CHRTRAN(xCrypt(gu_PSUserID),')','') + "/" +;
>>>> CHRTRAN(xCrypt(gu_PSUserPwd),')','') + "@" + gs_PSDataBase+" "+;
>>>> "-xcb -i" + lcPSIniLoc + " -m"+lcPSIniLoc+"allmaxes.max"+" "+;
>>>> "-o" + gs_PSTempLoc+"SQR.LOG"+" "+;
>>>> "-ZIF"+lcPSIniLoc+"pssqr.ini" +" "+;
>>>> ['CATS']+" "+['CATS']+" "+['CATS']+" "+lcParamString
>>>>
>>>>RUN &lcCommand && this is very the problem
>>>>**************
>>>
>>>So it is over 350 char long. Never tried such a big RUN commands. How about Ed's suggestion, does that work?
>>
>>Nick, I know that this command is very long, but it was interesting for me , why RUN/N1 doesn't care about the length? I didn't try Ed's idea.
>>Thanks.
>>Jerry
>
>Just a shot in the dark, but RUN command supports running DOS and Windows programs. When you issue RUN/N1 you clearly specify that it is a Windows program. Maybe that's where the difference is.

Nick, I think I know what is the problem.
When you use RUN command (no parameters), so by default this is a MS DOS call and VFP send it directly to OS,but because MS DOS supports command line not longer then 128 bytes, VFP replies with the message 'String is too long'.
Thanks for your ideas.
Jerry