Laurence,
Recently you provided us with an update to try and solve the drawing objects mysteriously appearing in our generated sheets. It was version 3.8.0.2. After we starting using this revision we began to notice strange things happening with our formula resolutions. We store the definitions for our columns in XML as you will see below. We have to escape any ampersands that we use for concatenation using &. What we are now seeing with this new revision is that if there is a quote mark in the formula definition that is next to the escaped ampersand (it doesn’t matter what size the quote is on) the formula will be generated with an extra quote mark inserted, therefore breaking the formula. We have changed nothing in the definitions to break this. The only thing we have done is implement 3.8.0.2.
Example #1
XML - =IF(MID(P@ROW@,1,1)=“E”,“0-”&(BD3100)&“%”,IF(MID(P@ROW@,1,1)=“A”,“0-”&(BD4100)&“%”," 0%"))
Resolves To…
=IF(MID(P22,1,1)=“E”,“0-“”&(BD3100)&“”%",IF(MID(P22,1,1)=“A”,"0-“”&(BD4100)&“”%”," 0%"))
and it used to resolve to…
=IF(MID(P22,1,1)=“E”,“0-”&(BD3100)&“%”,IF(MID(P22,1,1)=“A”,“0-”&(BD4100)&“%”," 0%"))
Example #2
XML - =TRIM(MID(K@ROW@ & M@ROW@ & AO@ROW@ & " " & AC@ROW@ & " " & L@ROW@ & " ",1,14))
Resolves To…
=TRIM(MID(K19&M19&AO19&" “”&AC19&“” “”&L19&“” ",1,14))
and it used to resolve to…
=TRIM(MID(K19&M19&AO19&" “&AC19&” “&L19&” ",1,14))
Again the only change was the new dll revision.
Thanks,
Scott