G
Guest
Hello,
I have a nested user define function in the Expression Build of a report.
The simple funtion works, but when I place a IIF() around it, Access does not
save the new logic and keeps doing a save as with the old logic. Is this to
complex for Access or am I doing something wrong???? Thanks in advance for
you help.
Current Working Function in Expression Builder used on a Unbound Field in a
Report:
=CalculateBuyOrSellDate([PayDate],[SellDay]))
New logic that Access will NOT save:
=IIF( IsNull([SellDay], " ", CalculateBuyOrSellDate([PayDate],[SellDay]))
What I wish to do is check for Nulls. If there is a Null, the print
nothing, otherwise, call the function I wrote and print the result.
- Mike P
I have a nested user define function in the Expression Build of a report.
The simple funtion works, but when I place a IIF() around it, Access does not
save the new logic and keeps doing a save as with the old logic. Is this to
complex for Access or am I doing something wrong???? Thanks in advance for
you help.
Current Working Function in Expression Builder used on a Unbound Field in a
Report:
=CalculateBuyOrSellDate([PayDate],[SellDay]))
New logic that Access will NOT save:
=IIF( IsNull([SellDay], " ", CalculateBuyOrSellDate([PayDate],[SellDay]))
What I wish to do is check for Nulls. If there is a Null, the print
nothing, otherwise, call the function I wrote and print the result.
- Mike P