Hello...

I am upgrading from ACA 2008 to 2011. In 2008, I was able to add custom paths in the support file search path that utilized Windows environment variables, such as %custompath%, and ACA would maintain that setting, and would resolve it in the Working Support File Search Path, as expected.

However, in 2011, I can enter the custom path, and ACA resolves it in both the SFSP and WSFSP, and when I close ACA, it saves the resolved path, not the environment variable, in the registry. This is counter-intuitive to the whole purpose of using the environment variables in the first place...

Does anyone know why this is working differently now, and if there is a solution to change it back to the way it worked in 2008, saving the environment variable string in the registry??

Thanks for your help!
Chris