Hi

> Another option is to copy the script file to a slightly different 
name and run both files.
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]

That's a very clever idea. One could even do this automatically with 
a small script. But one would produce a lot of scriptfiles and also 
have to check, if a scriptname already exists or not.

It would much more elegant, if Bruce could offer an option to run a 
script with an automatically generated unique-idenifier-extension, 
which Powerpro would have to handle internally, especialy concerning 
the scriptcache and error-messages, which might be a problem.
Something like:  
=> *script runfileuid scriptname 
or 
=> runfileuid.scriptname

If he could or would change the internal script-handling to generally 
working with such an extension (*script runfile would have extension 
space), that would be great and solve such problems. (By the way, 
this seems to be similar to *EXEC MoreCommandsAsScript.)

@Bruce: What do you think about that ?

Best regards Detlef


Reply via email to