Hi Alex I ran that test script. It reported good news: that PProTestvar became "Test1" and later "Test2". However, when I then opened a new cmd prompt window, "Set" did not include PProTestvar in its list and "set PProTestvar" produced: "Environment variable not defined"
So I concluded maybe just closing the cmd window with its X button does not fully close that instance of cmd.exe. So I closed it with an "Exit" command at the prompt instead. That did not fix it. In a subsequent cmd window, Set still doesn't report PProTestvar, even though your script did. ____________________________________________ I get the impression that PowerPro's exec.setenv() is always working, and affects how the envvar is interpreted in a Windows command, but that is not always reflected in a "new" cmd window. I suspect that the supposedly "new" cmd window is not making a fresh reading of the environment variables. ------------------------ 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/
