Go to SQL view of your query and post the entire SQL statement being used.
Appraised Value: IIf([Appraised Value]<=[Purchase Price], [Appraised Value], Null)
Purchase Price: IIf([Purchase Price]<[Appraised Value], [Purchase
Price], Null)
I'm sorry, but this cannot be copied directly from your query as Access
will not allow you to alias a query field with the same name as a field
inside the expression unless you include a table qualifier. What you have
there should be giving you circular reference errors. Please post the SQL
of the entire query or of a test query that is the smallest amount of SQL
that still produces the output in question.
Or you can try to break this down into manageable steps. Try the following
expression in your query...
IIFTest: IIf(1<=2, "First Value", "Second Value")
You should get "First Value" as your output. Then substitute different
numbers on either side of the <= operator, some with the first value larger
and some where they are equal. If you get this expression to work the way
you expect, then replacing the literal number values with your field names
should produce the same type of results. Once you get that you can replace
the text output values with one of your field names and Null.
I still feel we have a communication problem somewhere because an IIf()
expression that does a test and has Null as one of its output choices
simply cannot output a number under both test conditions. If you type the
expression wrong you will either get an error or get Nulls when you expect
numbers and vise-versa. There is no way to enter it wrong that will give
you numbers in all cases.
