#106 Invalid tasks that should not be there

[Tiberiu]

I have a .mpp file that when it is opened contains some tasks that should not be there. If I open this file in MS Project these tasks are not present. More exactly task "Core support" contains three tasks with null name that should not exist.

Thank you,
Tiberiu

[Tiberiu]

File with problem

[Jon Iles]

Can you try this with version 3.2.0?

Thanks!

Jon

[Tiberiu]

The test was made with 3.2.0.
With version 3.1.0 or 3.0.0 (not sure) besides those three above mentioned tasks there was another one immediately after the "Core support" task. Hence 3.2.0 removed that last task but not the other ones.

Tibi

[Leslie]

I have a file showing this same problem. I managed to pare the file down so it was very small, and attached below. Here is what mpxjQuery shows for the file:

Project Header: StartDate=07/08/2007 08:00 EDT FinishDate=07/08/2007 17:00 EDT

Resource: null (Unique ID=0) Start=null Finish=null

Task: Vault ID=0 Unique ID=0 (Start Date=07/08/2007 08:00 EDT Finish Date=07/08/2007 17:00 EDT Duration=1.0d Outline Level=0 Outline Number=0 Recurring=false)
Task: Team/financial performance ID=1 Unique ID=63 (Start Date=07/08/2007 08:00 EDT Finish Date=07/08/2007 17:00 EDT Duration=1.0d Outline Level=1 Outline Number=1 Recurring=false)
Task: null ID=320 Unique ID=437 (Start Date=22/04/2010 11:00 EDT Finish Date=23/04/2010 11:00 EDT Duration=1.0d Outline Level=4 Outline Number=null Recurring=false)
----------
(above edited)
The problem is with Task ID=320. You'll notice it doesn't have all the expected fields, and the outline level is definitely not good.

In trying to reduce this file to give to you, I did discover that the problem only exists if I read and write this file with Project 2003. if I use Project 2007 to write the file, the problem disappears. This is true, even if I write a Project 2003 format file from within 2007. So, it would seem to be a bug specific to 2003 (at least in my experience). However, Project seems to understand that this task is not "real" in the sense that it does not attempt to display it at all, even if I turn on custom fields specific to the fields that are set within task.

I (or actually a customer) stumbled upon this initially with mpxj 3.0. My further testing has been with 3.2. File attached below.

[Jon Iles]

Hi,

the code now in CVS fixes this issue.

Cheers!

Jon