Lag and elapsed time

Name: How to Lead Now!
Start: 2023-04-26T12:00:00-05:00
End: 2023-04-26T13:00:00-05:00
Location: Live Virtual Conference

Tagged: 2016, elapsed time, lag, Predecessor

This topic has 5 replies, 5 voices, and was last updated 6 years, 5 months ago by Betty Boushey.

Viewing 4 reply threads

Author

Posts
- 09/20/2016 at 4:39 pm #403706
  
  Betty Boushey
  Member
  
  Using Project 2016. In the Task Information box, enter a Lag of -50%. MSP keeps adding an “e” and assume for elapsed time.
  Back on the Entry table, in the predecessor column, can edit out the “e” or just type it out.
  Is this a new feature (yuck), a problem with the Task Information box or do I need to change an overall function someplace else?
  Thank you, Betty
- 09/20/2016 at 5:08 pm #403707
  
  Jigs Gaton
  Member
  
  Hi there Betty, I am not seeing that here. In the Predecessor Entry table, Lag column, it just shows -50% and the task seems to calculate correctly. Hmmm…
  - 09/20/2016 at 6:58 pm #403711
    
    Betty Boushey
    Member
    
    Thank you…confirms what I was expecting.
- 09/20/2016 at 6:49 pm #403710
  
  Larry Christofaro
  Participant
  
  Betty, I am getting the same behavior you are. Strange. I don’t use that kind of predecessor very often but never had the e entered automatically. I’m using Project Pro for O365. That does NOT happen on my Project 2010 version. Not sure what or when that happened, or if this is a bug or by design. Sorry for the lack of a good answer.
- 10/03/2016 at 4:45 am #404037
  
  Sai Prasad
  Participant
  
  This is definitely a BUG and not default behavior in Project 2016. This is reported to Microsoft and you should expect it to be fixed in the next update. Till that time, remove the “e” from the predecessor.
- 10/03/2016 at 11:28 am #404052
  
  Betty Boushey
  Guest
  
  Thank you! It is always nice to know it is a bug and a solution in the works! Made my day!93
Author

Posts