In my new job working for an Autodesk Reseller, it’s quickly become apparent what a pain in the backside enforcing single project files is in larger design offices. Single Project files, in most cases are a must when you have Autodesk Vault deployed within the company, but there is also a decent argument for employing the same approach with Autodesk Inventor. The main problem with enforcing this policy within these larger design offices, is the range in specification of the workstations, specifically varying hard drive letters.
Everyone has had a hand me down PC at some point in their career, it was probably at least 3 years old by the time you had it, right? Well as time marches on, those PC’s inevitably require some form of upgrade, RAM, GPU or Hard Drive. It seems there are a number of PC’s out there which have needed larger secondary hard drives installed, I’m not entirely sure why they are necessary when you have network storage, nevertheless this is the reality. The trouble comes in those scenarios because the CAD data is often stored on these secondary hard drives…. which means the drive letter the CAD data is store on varies from PC to PC within the office. Pre-Inventor 2013 you could rely on the relative paths in the Inventor Project File sorting themselves out as you moved it between hard drives, the drive letter just didn’t matter. It has always mattered with Vault when it comes to enforcing the Working Folder, which from a CAD Management perspective is highly desirable. Along comes Inventor 2013 with it’s shiny new Materials and Appearance libraries… If you need to modify any of the stock Materials or Appearances, then Autodesk recommends you create a custom library, rather than editing the default Inventor one. The trouble is, these Material and Appearance library files don’t follow the same relative path rule, they are full paths…. which means their path includes the drive letter. Arghh!
There is a fairly easy workaround though, hopefully Autodesk tidy this problem up someday. In the meantime check out my video below to see how combining a local share and mapping a network drive will save your bacon.
Image Credit: William Warby