--- Bruce wrote: > The other fact is that the system's ExpandEnvironmentStrings command > does not tell PowerPro whether there were any strings expanded when > PowerPro asks it to check a command line. So when PowerPro finds a % > in a command line, and calls that routine, it assumes that a new > space could have been introduced, and sometimes gets confused about > how to separate the command file from the parameters.
Would it not be possible to extract the command line from the unexpanded data, and then act upon that? It seems to me that this would make the checking for spaces and/or double quotes far more trivial, since spaces cannot be introduced midway. My apologies if I have missed something in your response. -- Alex Peters / Melbourne, Australia PowerPro v4.1.00 / Windows XP ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
