Yes John is right.I used to have same problem.I knew RD was not enough, so used to change the ligic.
cheers

No sweat. Hopefully you’re not being sarcastic!?

The reason: retained logic calculation mode coupled with progress shown on an RD basis coupled with the RD being less than the number of working days between the DD and the activity EF date shown (with the activity EF date being effectively driven by its predecessor(s) -- i.e., retained logic).

Each instance where the progress visually "extends beyond" the data date will be itemized in P3’s (v3.1) scheduling diagnostic (in the section titled: "out of sequence progress"). This could become a VERY long-winded discussion re: merits of retained logic and whether all of these things must indeed be cleaned-up (my take: 1. retained logic is good; 2. understanding each instance where retained logic drives finish dates beyond the RD is of utmost importance to a scheduler) -- but suffice it to say, you can either keep things as-is (after you understand WHY the schedule is doing what its doing) -- or - if for some reason you don’t want to see progress represented in this fashion, you will need to modify predecessor logic and/or the activity’s RD in order to make the progress bar "stop" at the data date. You can also switch to PC for visual representation of progress, but then you don’t get the nice visual cue that retained logic is having an effect on dates. Also, note that float values will be dictated by any and all keystrokes and mouse-clicks you make in this regard.

JF

I’ve noticed the same Kevin, but havent been able to find
the exact reason for it yet.

One thing I’ve noticed though, is that, under Format-->Bars
if we choose to show progress based on % complete, its
different from that shown based on remaining duration.
But in either case, some or the other bar shows progress
color beyond the data date. ??