> On Sep 26, 5:20 pm, Carl Henthorn
> <CarlHenth...@discussions.microsoft.com> wrote:
>> you're really better off modifying the query code to replace NULLS with
>> blank
>> strings before the rpt code even looks at it. anything else will be an
>> epic
>> kludge.
>>
>> "r...@mgk.com" wrote:
>> > since the IIF statement evaluates both the true and false conditions
>> > regardless... I need to find a replacement to it...
>>
>> > my code is:
>>
>> > =IIF(Fields!SOURCE_TRANSACTION_KEY.Value = nothing, "", Fields!
>> > SOURCE_TRANSACTION_KEY.Value.TOSTRING.SUBSTRING(3, 2))
>>
>> > I get the #ERROR value in my report for values that are null since the
>> > SUBSTRING of a NULL value generates an error.
>>
>> > I've tried CHOOSE and the SWITCH and they behaved as IIF.
>>
>> > I do not want to handle this on the server side.
>>
>> > Any ideas?
>>
>> > Thanks
>
> argh! was hoping to avoid that...
>

<CarlHenth...@discussions.microsoft.com> wrote:
> you're really better off modifying the query code to replace NULLS with blank
> strings before the rpt code even looks at it. anything else will be an epic
> kludge.
>
> "r...@mgk.com" wrote:
> > since the IIF statement evaluates both the true and false conditions
> > regardless... I need to find a replacement to it...
>
> > my code is:
>
> > =IIF(Fields!SOURCE_TRANSACTION_KEY.Value = nothing, "", Fields!
> > SOURCE_TRANSACTION_KEY.Value.TOSTRING.SUBSTRING(3, 2))
>
> > I get the #ERROR value in my report for values that are null since the
> > SUBSTRING of a NULL value generates an error.
>
> > I've tried CHOOSE and the SWITCH and they behaved as IIF.
>
> > I do not want to handle this on the server side.
>
> > Any ideas?
>
> > Thanks