Restrictions in Expression Builder
Why not just not use the expression builder quite so much?
Heavily depending on a piece of UI that is widely regarded
as the worst piece of UI right after the security UI is a
mistake, IMHO. Its worth neither "killing you" nor "a whole
lot of time" just because you find a limitation.
Michael
Quote:
> This works as source for a report footer control:
> =Sum(IIf(((([Final Disposition]="Use As Is (Reference
Authorization in
> Comments)") Or ([Final Disposition]="Move to Closeout
Location")) And ([Date
Quote:
> Closed]>=[Forms]![frmDateRangeSelect]![ctlDateIn]) And
([Date
Closed]<=[Forms]![frmDateRangeSelect]![ctlDateOut])),[Closin
g Total
Quote:
> Cost],0))
> But if I add one more condition to the true part of the
IIf
> { ([Team]="A") } as follows, I get an #Error as the
returned value.
> =Sum(IIf(((([Final Disposition]="Use As Is (Reference
Authorization in
> Comments)") Or ([Final Disposition]="Move to Closeout
Location")) And ([Date
Quote:
> Closed]>=[Forms]![frmDateRangeSelect]![ctlDateIn]) And
([Date
> Closed]<=[Forms]![frmDateRangeSelect]![ctlDateOut]) And
> ([Team]="A")),[Closing Total Cost],0))
> If I remove one of the other "And" conditions, it works!
> Is there a limit to the quantity of conditions that can be
handled by the
> IIF functions.
> This is killing me (and a whole lot of time).
> Thanks in advance,
> Joe
