(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?
(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.
How often would you upgrade your P6 to the latest version? I know people that refused to upgrade and they are still using P6 v6 and it works perfect for them. They are basically doing the same job I am doing with my v15.2. It appear that primavera makes its money from the yearly support fee but is it really worth it to pay for the year support after the first year you are required to buy. At the current rate, the yearly support fee will buy a new P6 licensce in the 5th year. Would you pay for the support on a yearly basis or buy a new P6 license every 5 years. What do you think
Printer-friendly version
Send to friend
I agree P3 to p6 is a major change and aan advantage but I do noe see it either within p6
Thanks Zoltan,
I dont forsee any of the items listed ever been a major issue. I would prefer not to do a regular ugrade unless we absolutely have to. Maybe upgrading from P3 to P6. The only benefit I see to the yearly support is the ability to talk directly to oracle agents. Most of my P6 issue can sometime be troubleshooted with google.
Thanks Zoltan,
I dont forsee any of the items listed ever been a major issue. I would prefer not to do a regular ugrade unless we absolutely have to. Maybe upgrading from P3 to P6. The only benefit I see to the yearly support is the ability to talk directly to oracle agents. Most of my P6 issue can sometime be troubleshooted with google.
I think it largely depends on a couple of different things.
1. CON then PRO Being able to import a newer version of an xer file yes of cource you can trick the xer file by changing the first line of the header but in version P6 15.2.3, Primavera has added a checksum to the XER and XML files to “identify whether the XML/XER has been modified externally”. That would prevent you from changing the header of the file. Howerve in P6 15.2.5, they have removed the checksum.
2. CON then PRO Do you want to have that capabilities of using any of the NEW features. i.e 8.2 added line numbers and have the ability to color code activity codes as well as resource.
3. CON fall 8.2 was the cost account function is thru a broswer interface. Very Cumbersome (changed back in version 15)
4. CON fall if you have written any in-house P6 training manuals they will have to be re written based on the new features especially if you are using scren shots in your manuals. This is a huge undertraking.
maybe if it aint broke don't fix it.
Email: PPadmin@planningplanet.com
Replies