If you are defining the variable or changing it after Essbase has been started I do not see how Essbase itself will ever respect the variable. If I recall my assembly from years ago the environment variables are stored within the process's memory starting at runtime -- this is why if you defined a new variable you would have to stop and start the process for the variable to be visible.
Suggest you pass the env variables as parameters rather than refer to env vars.
John A. Booth
Scoring disabled. You must be logged in to score posts.