Well seems like an incomplete posting of html code resuls in an error on the hole page instead of just in my posting. Probably this is an issue PP Web developers can deal with as to limit the display to within the posting frame or even better to detect the error and just post the incomplete code so the person doing the post can access it and fix it.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
Mike, can you delete the incomplete HTML code from my prior posting?
OK This once only - But your dancing frog gets it.
One more time, could you please explain how you "attach" these screenshots? I know it doesnt waste any space on PP-servers as it is basically only a link to some other remote server, but...how?
This kind of logic I have seen to be very common on MS Project users, I call it "M.T. Logic", any similarity to a PP member name is pure coincidence.
The problem starts with the PDM computation on Early Start of activity B, P3 solve the issue by allowing splitting. Then after the activity consumes what I call "intermittent float" (don’t know if the term already exists or if other name is used) any further increase in activity duration start consuming Total Float.
A few days ago I found this article related to this issue.
The problem is most probably related to a FF-link somewhere in your schedule as Mike also indicates. MSP operates with start slack and finish slack and the smallest of those 2 equals the total slack.
That means that an activity can have start slack of 0, thereby being critical, but maybe a finish slack of 5 days and the total slack will be shown as 0. If you increase the duration with 3 days, I would as you expect a delay of 3 days as the total slack = 0, however, no delays happens, just a change in finsih slack from 5 days to 2 days.
Unfortunately, MSP doesnt (at least my version) show the correct values of either start slack or finish slack, it always makes one equal the other and thereby equal the total slack, i.e. all 3 have the same value. Maybe a have a wrong setting somewhere.
Anyway, the increase in total slack when increasing a duration (sounds contradicting) can happen when you have a FF-link somewhere in the middle. A small test in MSP: Say you have 4 activities, a(8days), b(8days), c(8days) and d(20days). b is linked from a with a FF+6days link, c to b with SS+3days link. d not linked to anything, but having same start date as a. Both a, b and c will have total slack of 3 days.
Now increase the duration of b from 8 days to 10 days. You would expect the total slack to go from 3 to 1 day for some of a, b or c. Unfortunately, it will increase from 3 to 5 days for a, b and c, even though you have increased a duration. The overall finish date is still the same, determined by ds duration.
Therefore, dont always trust the total slack value in MSP. Use e.g. Pertmaster or P6 instead as they clearly distinguish between Total Start Float and Total Finish Float. Powerproject only has Total Float (to my knowledge), based on the Finish Float (and that is all one need if only setting up programmes with FS-links).
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
Sorry about the late reply. But thank you all for the effort you have put in replying to my question.
Hi Rafael
Last time I saw a beaver like that it cost me 250 bhat and I was robbed.
Best regards
Mike Testro
Mike,

Thanks. Hope you won’t mind if a beaver.
A proud rat,
Rafael
Well this is how HTML looks.

Got him - he has croaked.
See Thread Nr 9 & 14
Mike or PP Admin,
Please after fixing my post no 8 delete all my subsequent posts as to give back this page to Stuart Atkinson.
No Chance sunshine - we are revelling in your embarasssment.
Best regards,
Rafael
May a new page be created!!!
.....
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
Well seems like an incomplete posting of html code resuls in an error on the hole page instead of just in my posting. Probably this is an issue PP Web developers can deal with as to limit the display to within the posting frame or even better to detect the error and just post the incomplete code so the person doing the post can access it and fix it.
I believe from prior observations that the error stop at the page andif you continue with nwe postings that create a new page it will stop.
Mike, can you delete the incomplete HTML code from my prior posting?
OK This once only - But your dancing frog gets it.
Hi Rafael,
One more time, could you please explain how you "attach" these screenshots? I know it doesnt waste any space on PP-servers as it is basically only a link to some other remote server, but...how?
Regards,
Bo
This kind of logic I have seen to be very common on MS Project users, I call it "M.T. Logic", any similarity to a PP member name is pure coincidence.
The problem starts with the PDM computation on Early Start of activity B, P3 solve the issue by allowing splitting. Then after the activity consumes what I call "intermittent float" (don’t know if the term already exists or if other name is used) any further increase in activity duration start consuming Total Float.
A few days ago I found this article related to this issue.
http://www.pmicos.org/topics/aug2006tom.pdf
Hi Stuart,
The problem is most probably related to a FF-link somewhere in your schedule as Mike also indicates. MSP operates with start slack and finish slack and the smallest of those 2 equals the total slack.
That means that an activity can have start slack of 0, thereby being critical, but maybe a finish slack of 5 days and the total slack will be shown as 0. If you increase the duration with 3 days, I would as you expect a delay of 3 days as the total slack = 0, however, no delays happens, just a change in finsih slack from 5 days to 2 days.
Unfortunately, MSP doesnt (at least my version) show the correct values of either start slack or finish slack, it always makes one equal the other and thereby equal the total slack, i.e. all 3 have the same value. Maybe a have a wrong setting somewhere.
Anyway, the increase in total slack when increasing a duration (sounds contradicting) can happen when you have a FF-link somewhere in the middle. A small test in MSP: Say you have 4 activities, a(8days), b(8days), c(8days) and d(20days). b is linked from a with a FF+6days link, c to b with SS+3days link. d not linked to anything, but having same start date as a. Both a, b and c will have total slack of 3 days.
Now increase the duration of b from 8 days to 10 days. You would expect the total slack to go from 3 to 1 day for some of a, b or c. Unfortunately, it will increase from 3 to 5 days for a, b and c, even though you have increased a duration. The overall finish date is still the same, determined by ds duration.
Therefore, dont always trust the total slack value in MSP. Use e.g. Pertmaster or P6 instead as they clearly distinguish between Total Start Float and Total Finish Float. Powerproject only has Total Float (to my knowledge), based on the Finish Float (and that is all one need if only setting up programmes with FS-links).
Regards,
Bo
Hi Stuart
Are you using multiple calendars - for instance a task set at 24/7 could end within a non-working period.
Are you using SS FF links with lead/lags?
When you move/increase the non-critical tasks what happens to the successors when you re-schedule? Do they move by the same degree?
Best regards
Mike Testro
No Gary,
incidentally, this occurs on numerous tasks.
i do have calculate multiple critical paths option on.
Does the activity have any sucessors, constraints or deadlines linked to its start rather than finish?
Thats the only reason I can think of.