There aren't any known problems or limits with that functionality. The chained process environment block will be inherited from the parent VBP process. Does the attached sample work properly (logging the XDK/XEDK environment variable values in both instances)?
Some things that could influence treatment of environment variables within VBP are
1) modification of 'Tools | Application Options | General | Include environment variables in system macros' (Application.Options.EnvVarsInSystemMacros in script code).
2) setting and/or deleting macros via a Set Macro action with 'Add to environment variables when calling external programs' checked.
3) Using the VBP object model to modify environment variables (see 'Environment Variables' section of the Advanced.bld sample).
|