Older projects, updating databases.

[cbenner]

Hi,

Am I missing something when it comes to moving projects created in an older release, to a newer release... that you have to manually remember to change the project properties to update the library paths and icon menus?  Because we keep finding projects, even new ones (copied from older ones), that are still looking for the AcadE 2013 or 2015 libraries and icon menus.  It would seem that, if you do your migration when upgrading, older projects would somehow see that the libraries they are pointing to are no longer there.... and maybe prompt you to change this?  If I'm NOT missing something (it is very possible that I am), I will set this up as an Idea.

[testsubject · Accepted solution]

Chris,

That is the case. You bring up a good suggestion though. 

I do not have this problem because I set up my system originally to point to the network folders (I removed all year dating references). Now when I upgrade and set it up for network access, all the old projects are still pointing to the same folders as before.

[cbenner]

@testsubject 

Hi, Bob.

I've been in the habit of keeping all of the old libraries for a while... "just in case", and using the release dates in my folders so I know which is which.  Maybe what I need to do is adopt your workflow so the paths stay the same (minus the release year), and tuck the JIC libraries away somewhere that I can still get to them if needed.  Belts and suspenders, I guess.  Thanks for the tip!

[rhesusminus]

Also, a few versions ago. the project file started supporting the %SL_DIR% variable, so your projects can point to for example %SL_DIR%/nfpa
This way, AcadE will find the correct path when opened in newer projects.

I recommend setting up the paths in your WD.ENV file, so that you easily can change the paths in old projects:
https://knowledge.autodesk.com/community/screencast/b4732c63-9701-4dab-980b-b387cd942703

If you need for the default path to the symbol libraries to point somewhere else, add this line to the end of you wd.env file:
SETQ:gbl_wd_baselibs,"X:/AcadE/Libs/"

[Anonymous]

This is really good topic.

Actually all these can be addressed by modifying the WD.ENV file. 

In our case, out of the box ACADE does not hit the ground running when it comes to aerospace design. As a default aerospace designs use JIC  (40%) symbols, most of the european DOAs work on metric drawing templates. So, we create almost all symbols (more than 90%) from the scratch. All symbols including the modified WD.ENV file will be saved / maintained in a common network folder. The modified WD.ENV file will take care of the settings we want. Thus ACADE version change does not affect the company / industry specific symbol libraries, settings, reporting tools etc.