Using Wildfire 4 M220 64-bit on Windows 7
We have network locations forcommon files referenced by the config.pro (e.g. pro_dtl_setup_dir, pro_symbol_dir, etc.). Every time the sys admins make a change to the config.pro, our Pro/E "breaks" because the drive letterat our site where these files are locatedis different than the drive letter where the sys admins are located. When we notice things not working correctly, we have to edit the config.pro file and change all the drive letters to the "correct" ones for our site.
I was experimenting with using environment variables so that a common "universal" config.pro could be used. Something isn't working. I remember doing this before at another company. Not sure what is different this time.
In the Pro/E start-up batch file there's an environment variable that sets the drive letter where these are stored
If I changed it back to a hard-coded drive letter, it worked again.