Edited ENV causes Environment file Button to fail and Reports to fail

[dennis]

I have a WD.ENV file edited to point to the network...and have used it successfully in 2013.  Now, in 2014, it will work as far as setting paths, but the Reports buttons no longer work nor does the Environment file button in Settings work.  Any ideas?

[dennis]

Well...i kept digging and tried the migration util on the edited WD.ENV...and now the buttons work...so answered my own question.

[dennis]

Further study has me a bit back to where I started the thread.  If I move the WD.ENV file to a network location, I still get the problem with the Settings/Environmet file button not working and neither do the Reports work at all.  Currently I have kept the migrated WD.ENV on the local documents/AcadE 2014/Aedata folder but I would like to move it to a share folder.  Is there any white papers / definative instructions on customizing the setup of AcadE?

[dougmcalexander]

2014 introduced some new languages and a language folder in the path for such things as the PLC database, catalogs, etc. A WD.env file from a previous version might need some tweaking to accommodate 2014.

[dennis]

Thanks Doug, wouldn't it be nice if these kinda things were documented somewhere.