Progress Line Disappears

Thank-you, Sir.  I am an old veteran.  I can easily create new bar styles and develop derived data based on formulas, etc.  I am familiar with that.  I appreciate your reply.  I developed red, yellow, green "stoplight dots" based on a float threshold range... 20 years ago!  Honestly, regarding the disappearing progress line issue, I am not very interested in "internal" MSP workarounds.  As I said, it is pretty easy to go into Bluebeam after-the-fact and insert a vertical line with a "Status Date" text box at the top (right under the calendar timescale) and then paste THAT onto every page of the schedule report (akin to what MSP was doing prior to this issue cropping up).  Fairly easy.  But still, a pain.  What really irritates me is that, as I said, this program, on a standalone basis, is basically the same as it was in its "Project 98" incarnation.  Granted, in an "enterprise" setting, there is probably a lot more capability now -- but my guess is that this additional capability is primarily a function of the evolution of the network environment and various database add-ons apart from the native MPP file.  Don't get me wrong... I don't bow-down to the altar of any piece of scheduling software.  I like MSP!  And it is even good middleware.  I do a lot of quick/initial schedule development using MSP... because it is EASY.  And then, an XML import into P6 generates a nice clean WBS... with only a teeny bit of cleanup and fussing to do afterwards.  P6 cannot easily deal with "cut-and-paste" external data from various sources (which is what a LOT of scheduling on big projects entails -- gathering information from multiple/myriad team players and trying to AVOID typing everything over again).  P6 has other issues, too.  I have a list as long as my arm.  Why can't Oracle fix these things?  Pretty obvious if you are a regular user.  But P6 is just a tiny sliver in Oracle's world.  Just like MSP is a tiny sliver in Microsoft's world.  Back to MSP... for example, if you are doing any sort of serious project management scheduling work and schedule delays are not fully resolved by a contract modification... you have... negative float.  The fact that MSP cannot (without apparently developing some sort of sophisticated high-level coding or advanced custom variable definition) selectively display the "critical" highlight/color based on a NEGATIVE float value (i.e., only a POSITIVE threshold is available -- see FILE->OPTIONS->ADVANCED... and go to the bottom of the pop-up window)... this is frankly inexcusable.  Let alone displaying "longest path" (akin to P6) where there may be a mix of float values -- depending on the calendar assignment -- on the same sequence path.  So... in MSP, I have to continually reset the "Finish no Later Than" constraint date on the terminal node to match the "early" date -- in order to display only the longest (critical) path in red.  But then, the longest path float value is "zero" (as opposed to the desired negative number).  Again, I am a 40+ year veteran and over the years I have worked for a couple of software companies (CPM scheduling software) and I'm pretty sure that it would be fairly simple to implementing "feature" -- not hard thing to code.  Which speaks to the act that Microsoft is putting ZERO effort and resources into MS Project... and the fact that NOBODY within Microsoft (directly) will every investigate this issue.  It has always been the odd stepchild of Office.  Anyway... thanks for the reply... I appreciate it!  My guess is that one of these days the Progress Line will magically reappear... due to some sort of Windows Update being applied.  Or whatever.  That's just the nature of the business, I suppose.  Would be nice if someone with actual product authority/pull would read these forums and take action.  But when you're the 2nd biggest company in the world (market cap) and life is soft... then why bother?  But we small people have to complete.  Sorry about the rant.  From a customer service standpoint, I supposed this issue now goes into the "resolved" category.  THANKS again, Sir!