Assignments and Null Values

[mmemon]

Hello.
I can't understand why this behavior is happeniing. I have the below formula in 1 report and it works fine:

Local stringVar upsSenior;
if{CNTR_ATT_UPSSAO_V.ATT_TYPE}<> &quot; &quot; then
upsSenior:=&quot;...Same As Office&quot;
else
upsSenior:= {PRODX_ADDRESS_UPS_V.STREET1} + &quot; &quot; +{PRODX_ADDRESS_UPS_V.STREET2} + &quot; &quot;+{PRODX_ADDRESS_UPS_V.CITY} + &quot;,&quot; + {PRODX_ADDRESS_UPS_V.STATE} + &quot; &quot; + {PRODX_ADDRESS_UPS_V.ZIP};


However, I add the same logic to another report and a null value is displayed instead of the entire address. And what I have concluded is that if Street2 is null, null is assigned to upsSenior. Does anyone know why if street2 is null, why 1 report still shows the other fields while the other report shows nothing for the fields.

 

[synapsevampire]

One report may have the File->Report Options-> Convert null values to default turned on, which resolves this sort of thing.

-k

http://www.informeddatadecisions.com

kai@informeddatadecisions.com

 

[mmemon]

Thank You.
That was it.
Michele