Forum Discussion
Re: Detailed question about comparison of 2 Microsoft Project files
I actually just realised that even though in the source files (file A and B) the Unique IDs are the same (number 1-400) when I displayed Unique ID in the comparison view it had the numbers going up to 800 so I'm not sure what to make of that...
3 Replies
- After some more googling, I'm starting to wonder if it is actually the GUID that is the factor. As I can see that column has different values in the two files. So I'll explore that to see if it helps.
I've never tried to run a comparison on two files that were generated by code. By default they would not be "genetically" related which is the basis for comparison.
The original Compare Projects utility did use the Unique ID as the reference. However, it had some issues and it wasn't until (I believe) release of Project 2010 that the utility was finally "fixed". It is possible that it now uses the GUID as the reference, I don't know.
Since you are trying to compare two files generated by a macro you will most likely need to create your own unique reference so the files can be compared, and write your own compare macro like I did many years ago.
Good luck.
John
- I think I may have answered my own question for that last comment. I assume in the act of creating a comparison file (effectively a master project) it starts its Unique IDs from scratch thus leading to the ids going up to 800.
However I am still in the unique positions where if I take one of my files, slightly modify a date, and compare, the comparison report successfully shows it. Yet if I take my two 'seemingly identical' files generated from a macro, and slightly modify one, the comparison report thinks it is an entirely different Project and shows the whole file as being different. Help!
