--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "evanascott2002" <evan.scott@> > > > The above worked for me if I added configure.restart at end. > > > > > O frabjous day! Callooh! Callay! So right you are. And the code is so > > much more elegant than the copy solution would have been... assuming > > After mounting that jabberwocky pelt, and thinking of the next thing > to do, make sure you won't call this code from script running from a > command list, as the reconfigure restart will delete the command list > from memory, and PowerPro will abort. > > Calling from a script file should be OK. > Ah so desu! Perhaps I will add this as a comment in the script file in case some other fine PowerPro programmer type gets a bright idea. For the most part I tend to favor external scripts if only because I can resurrect a broken run by adjusting (or commenting out) code in my handy-dandy editor whereas if it is a script running from a command list it is pretty much necessary to restore from a backup. Also I have added highlighting to Textpad for the PowerPro keywords and that makes it much easier to see what I am doing.
Thanks for the tip. evan 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/
