J
John D.
Goes on ...
This is not a valid duration, or is outside the range for this field ....
By [blank] I mean the normal text for the column name is missing. As if the
column it's seeing the error in has no name.
This was also followed with the same error for the Basline Fixed Cost
Accrual Column
Occurs while cutting and pasting a summary task in schedule that has been
inserted to another schedule. Happens in both the sub schedule alone and in
the consolidating schedule.
This came on yesterday and had not been an issue all last week.
It is reproducible by my ISP's tech support.
Tried to date:
XP Sp3
MS Project Pro 2007 - SP1
Creating a different view and doing the cut -n- paste from there.
There was on article in the MS knowledge base that was not useful.
I can get it to go away by saving down to 2003, doing on cut-n-paste and
then using that new task group going forward with subsequent cut-n-pastes.
I'm guessing somewhere in the process one or more bogus columns are showing
up in the schema, but I have no way that I know of to find it.
Any help would be appreciated.
Hope this is being posted in the right forum.
Best,
John D.
This is not a valid duration, or is outside the range for this field ....
By [blank] I mean the normal text for the column name is missing. As if the
column it's seeing the error in has no name.
This was also followed with the same error for the Basline Fixed Cost
Accrual Column
Occurs while cutting and pasting a summary task in schedule that has been
inserted to another schedule. Happens in both the sub schedule alone and in
the consolidating schedule.
This came on yesterday and had not been an issue all last week.
It is reproducible by my ISP's tech support.
Tried to date:
XP Sp3
MS Project Pro 2007 - SP1
Creating a different view and doing the cut -n- paste from there.
There was on article in the MS knowledge base that was not useful.
I can get it to go away by saving down to 2003, doing on cut-n-paste and
then using that new task group going forward with subsequent cut-n-pastes.
I'm guessing somewhere in the process one or more bogus columns are showing
up in the schema, but I have no way that I know of to find it.
Any help would be appreciated.
Hope this is being posted in the right forum.
Best,
John D.