Yard
Well-known Member
- Joined
- Nov 5, 2008
- Messages
- 1,929
Hi,
I have a calculated field (OSDays) which uses other calculated fields (OSDay1, OSDay2, OSDay3) to produce a result. OSDays reads:
= (OSDay1+OSDay2 +OSDay3 )/SUM(MthD1Test)
where MthD1Test is a data field in the source.
This works fine, but it seems that when the file is closed/re-opened, OSDays becomes (intermittently) corrupted to
= (#NAME!+#NAME! +#NAME! )/SUM(#NAME!)
Other calculated fields in the PT are unaffected, but it seems any calculated field which takes the result of another calculated field is prone to corruption.
I have the option to re-create the calculated fields via VBA on Worksheet_Open, but I'd like to know if there's something I'm missing here, or is it a known bug?
Thanks
Yard
I have a calculated field (OSDays) which uses other calculated fields (OSDay1, OSDay2, OSDay3) to produce a result. OSDays reads:
= (OSDay1+OSDay2 +OSDay3 )/SUM(MthD1Test)
where MthD1Test is a data field in the source.
This works fine, but it seems that when the file is closed/re-opened, OSDays becomes (intermittently) corrupted to
= (#NAME!+#NAME! +#NAME! )/SUM(#NAME!)
Other calculated fields in the PT are unaffected, but it seems any calculated field which takes the result of another calculated field is prone to corruption.
I have the option to re-create the calculated fields via VBA on Worksheet_Open, but I'd like to know if there's something I'm missing here, or is it a known bug?
Thanks
Yard