Drivin predecessor/successor info in SQL DB

• http://www.austprojplan.com.au/relationship-float-and-viewing-in-primav…
• http://www.ronwinterconsulting.com/The_Inner_Workings_Of_P6.pdf
• Keep in mind P6 calculations for resource leveled floats are unreliable and that P6 Longest Path calculations break under resource leveling.
• http://www.planningplanet.com/forums/planning-scheduling-programming-di…
• https://docs.oracle.com/cd/E17462_01/Web_Access/Help/en/Projects/Tasks/…

Tom is right. Instead of old Btrieve P3 database P6 doesn't store information regarding driving predecessors, relationship float etc in database. In order to get proper access to this data you have to use Primavera API.

Regards,

Andrew

• There is software to get this information from P6 such as Schedule Analyzer 
• http://scheduleanalyzer.com/ll_brochure.htm
• I wonder if by clicking on the field name on the screens that it is available you will be able to get the code, then somehow you will need to figure out the name of the database table.
• http://www.ronwinterconsulting.com/Extended_Relationship.pdf 
• http://www.ronwinterconsulting.com/Making_CPM_Transparent.pdf
• http://www.ronwinterconsulting.com/Longest_Path_Value.pdf 
• There will still be missing some relationship calculations such as: 

1. In-Progress Lag Report and Value. Remaining Lag should be displayed just as remaining duration is shown and editable. The CPM feature of Remaining Duration was added so that Schedulers could monitor and change this calculated duration result. Lags are to relationships what durations are to activities. Why should Remaining Lag calculations be discarded by the software instead of saved and displayed? Why should we be unable to indicate that Actual Remaining Lag is only 2 days instead of the calculated 4 days?
2. Also Relationship Slack should be displayed; the amount of inter-activity float a relationship has in relation to other relationships with the same successor activity, measured in the same units as float for the schedule involved.
3.  Part of the reason CPM Schedules are so hard to understand is that fact that not all of the data used is displayed.

• You can make some of the equivalent data visible if using activities to model links & lag, but this is impractical for most of us. For 0 lag use a milestone. In these activities; Actual Duration will be the equivalent to In-progress Lag Lag, Remaining Duration will be the equivalent to Remaining Lag and Free Float equivalent to Relationship Slack.
• I use different software and it gives me a similar table without need of additional software. Same as P6-Logic_League it misses to display some of the data, data discarded and not stored in the database. 
• Keep in mind P6 calculations for resource leveled floats are unreliable and that P6 Longest Path calculations break under resource leveling.
• http://www.planningplanet.com/forums/planning-scheduling-programming-di…cpm-longest-path-theory-broken-under-resour
• https://docs.oracle.com/cd/E17462_01/Web_Access/Help/en/Projects/Tasks/pm_cpm.htm

• Therefore I would not trust P6 calculations on resource leveled schedules.
• Good luck,
• Rafael

[Duplicate Delete]

I could be mistaken, but I managed to convince myself that relationship free float (and the associated "driving" flag) are not stored in the database but are instead computed and displayed by the client application.  Your reporting application would have to compute it independently - not a trivial exercise because it requires calendar math.