Thanks to a question asked by Ben, I thought of posting this write-up; MS Project 2010 has 32 bit color, so it has rich set of new and mesmerizing color set in its font color option which include Orange and variables shaded of blue and green. While MS Project 2007 has 16 bit color, so saving a 2010 font formatted file have impact when opened in 2007.
Here goes the list :
1. Orange could change to Red, lighter shades of Blue can turn to hyperlink blue etc. Implying that newer shaded of 2010 changes to some nearby shades in 2007.
2. Strike through tasks are not deleted in 2007, but strike through is removed.
3. Inactive tasks are deleted.
4. Manually scheduled tasks become Auto, as well constrains are set on them to trace their manual start or finish dates.


Other then that :
When you convert a Project 2007 file to a Project 2010 file, Project will operate in fully functional mode and not in compatibility mode. However, Project’s default behavior for new tasks will differ from new files that are created in Project 2010.
1. Existing Tasks of 2007 will remain to Auto mode in 2010.
2. New tasks created would be in Auto mode by defualt, unless changed to manual.
3. Task Mode column won’t be displayed by default and need to be inserted.
4. Master Project, displays with full functionality, but only those subprojects which are converted to 2010 would expand rest won’t.
5. Cross-project links from Project files that have not been converted to Project 2010 and that are contained within a file that has been converted to Project 2010 cannot be expanded. Cross-project links that are converted to Project 2010 can be expanded.
6. Resource Pool using projects when converted to 2010 would need Resource Pool also to be converted to 2010.
7. Fields used in Formula in 2007 would change to its equivalent fields in 2010.
Will list more points, as I come across, these are some very top level observations.
Read Full Post »