It is widely known that conversions to and from P3 and P6 will create discrepancies. There are dozens of known issues and bugs that never seemed to get rectified. Casual observance shows that there are more problems going from P6 to P3 than from P3 to P6. It almost seems like Primavera did not want their P6 users to export schedules to P3.
You cannot use Claim Digger to compare a P3 schedule to a P6 one. We at Schedule Analyzer Software responded to this deficiency by creating the ‘Compare P3 to P6’ module in our Schedule Analyzer Enterprise Forensic (eForensic) software series. It compares the actual P3 data in the Btrieve database with the corresponding P6 data in the P6 database. You would be amazed at the number of ‘minor’ decencies and the number of major ones in a typical conversion!
Member for
22 years 10 monthsAnthony, It is widely known
Anthony,
It is widely known that conversions to and from P3 and P6 will create discrepancies. There are dozens of known issues and bugs that never seemed to get rectified. Casual observance shows that there are more problems going from P6 to P3 than from P3 to P6. It almost seems like Primavera did not want their P6 users to export schedules to P3.
You cannot use Claim Digger to compare a P3 schedule to a P6 one. We at Schedule Analyzer Software responded to this deficiency by creating the ‘Compare P3 to P6’ module in our Schedule Analyzer Enterprise Forensic (eForensic) software series. It compares the actual P3 data in the Btrieve database with the corresponding P6 data in the P6 database. You would be amazed at the number of ‘minor’ decencies and the number of major ones in a typical conversion!