Programmatically changing external task paths RRS feed

  • Question

  • Hi folks,

    Does anyone have any words of wisdom for a way to use VBA to change the paths of external predecessor / successor  tasks from a server-based path to a local path?  Basically, I'm trying to replicate a collection of cross-linked (predecessor / successor only) files from Project Server 2010 on a local file system by changing the path of an external pred / succ to point to the local copy.  The goal is to make it easier to experiment with the files in question without the risk of stirring up problems in the Project Server originals.

    There's about ten files involved with over 1200 tasks, and 2010 occasionally crashes when we try to open more than one at a time, which might have made this a bit easier.  (Lots of cross-links in some of these in these files.)

    I tried a few different techniques for doing this, but inevitably Project starts acting a little strangely, claiming "File not found" for file path strings that I actually test with a File System Object before asking Project to switch the reference.  I've also had some behaviors in the project's task collection that make me suspect the project task collection "bounces around" when the external links are being changed from one path to another, so the problems I'm having might also be some kind of recalculation race condition.  All of the files in question are present on the local system when I try to do these techniques.



    Monday, July 15, 2013 10:41 PM

All replies

  • linearprism,

    First let me say that I think you are playing with fire, especially in Project 2010. Linked structures in Project have always been fodder for corruption but Project 2010 appears to be even more sensitive. It may be possible to do what you want, but personally I wouldn't try it.

    That being said, there may be another approach worth considering. I have a macro that converts a dynamic master file with links between subproject tasks into a static master where the external links have been converted into normal predecessors and successors. Obviously this process "divorces" the files from the link structure and that may not allow you to do the "experimenting" you mention. The macro is not freeware.

    If you are interested, you can contact me at the address below.



    (remove obvious redundancies and the 7th character is a letter)

    Tuesday, July 16, 2013 12:31 AM