Or a User Defined Function that the Stored Procedure calls.
"Robert Bruckner [MSFT]" <robruc@online.microsoft.com> wrote in message
news:uO3ZYBwvFHA.252@TK2MSFTNGP09.phx.gbl...
> There is no limit on the length of an expression (other than limits imposed by
> the VB.NET compiler).
>
> In your case, you may want to look at alternatives to the IIF function:
> * =Choose(...)
>
http://msdn.microsoft.com/library/en-us/vblr7/html/vafctchoose.asp > * =Switch(...)
>
http://msdn.microsoft.com/library/en-us/vblr7/html/vafctswitch.asp >
> In addition, you may want to consider writing a function in custom code or as
> custom assembly that contains your logic. You can then reuse the function from
> RDL expressions.
>
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "g3kamdbs" <g3kamdbs@discussions.microsoft.com> wrote in message
> news:2A1DC075-220C-4494-AF82-157760B3EBD5@microsoft.com...
>> Is there a way to store an expression inside a table, and have the expression
>> being pulled from the table to execute during run time? I want to dynamically
>> create an expression based on the value of a column of the table. Using the
>> IIF statement will work but it's going to be a very long nested IIF..... and
>> that brings to the second question -> is there a limit for the length of an
>> expression?
>>
>> Thanks in advance.
>
>