Morgan

Update: It's not random. The<DurationFormat>tag seems to be set wrongly to 20 (elapsed percent) instead of 7 (days, I think). I created a file with multiple tasks starting at 1 day long and increasing by 1 day for each task. In the xml file it is saved as a duaration of 1H40M (100 mins), then 2 days is 3H20M (200mins) and so on, add in 100 mins per day to the time. Could it be adding 100% as mins? When it is reopened it then displays as 1day as 38.903 days 2 39.194 3 39.372 4 39.485 5 39.599 6 39.663...

Update: It's not random. The <durationformat> tag seems to be set wrongly to 20 (elapsed percent) instead of 7 (days, I think). I created a file with multiple tasks starting at 1 day long and increasing by 1 day for each task. In the xml file it is saved as a duaration of 1H40M (100 mins), then 2 days is 3H20M (200mins) and so on, add in 100 mins per day to the time. Could it be adding 100% as mins? When it is reopened it then displays as 1day as 38.903 days 2 39.194 3 39.372 4 39.485 5 39.599 6...

I have a similar issue that I think is related. All of my task durations have jumped up to 40 days, +/- a few hours/mins (seems random). All except the 0 day duration milestones. This is the same thing I see when I open the re-saved version of the OPs files. The strange thing is when I open up the tmp backup files, they are corrupted as well, but look ok in xml viewer. When I open the xml and resave as xml, the file changes drastically and increases in size from 600K to 2.2M