[epu]

~~~~~~~~~~~~~
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)?
~~~~~~~~~~~~~

The test you gave me prints it out in the parent and the chained instance.

I'll see if I can reduce my error to a smaller test case; I have a lot of steps.

~~~~~~~~~~~~~
1) modification of 'Tools | Application Options | General | Include environment variables in system macros' (Application.Options.EnvVarsInSystemMacros in script code).
~~~~~~~~~~~~~

I don't modify this value in either parent or child.

~~~~~~~~~~~~~
2) setting and/or deleting macros via a Set Macro action with 'Add to environment variables when calling external programs' checked.
~~~~~~~~~~~~~

In the parent file, I load a large set of global macros when I start the project with a script action:

<code>
Application.Macros(vbldMacroGlobal).Load "%PROJDIR%\COMMON.macros"
</code>

adding this to the test case does not reproduce the problem.

I'll try simplifying my project until I have the smallest proj that still reproduces the error and get back to you.

Thanks,
-e