I had been using User Environment Variables instead of System Environment Variables.
Also I was unnecessarily/inadvertently overridding the variable in the General:Model:EnvironmentVariables property.
If I remove any reference to the variable from rhapsody.ini and the project properties, then I can simply use $myEnvVar directly in a path field.

-------------------------------------------------------------------------------------------------------

I use Rhapsody from within Windows and Redhat Linux.
If my project contains a reference package - I have portability problems.

I have a shared folder which both Windows and Redhat can see called devshare.
On Windows the path to the ref pkg is say, C:\devshare\myPath, whereas on Redhat it would need to be say
/mnt/hgfs/devshare/myPath.

Surely there must be an easy way to make this path portable (maybe using environment variables)?
The only workable solution I can think of would involve editing the (windows) rhapsody.ini and (linux) rhp_env files. I'd rather not do this if possible.

Can Rhapsody READ a system environment variable? Anyone know another way?