Using IIF statement with a crosstab query (2000 SR-1)

Topic

New Reply

I have an application that is used for tracking employees

Reply | Quote

Replies

You could try this:

WHERE tblTaskNumbers.TaskNumber Like [Forms]![frmReportPrinting]![txtTaskOrderNumber] or Forms]![frmReportPrinting]![txtTaskOrderNumber] is Null

This has appeared a few times in the last few months in this forum, I think it was MarkD who originally worked this one out.
Pat

Reply | Quote

All that creating a parameter does is make the query aware that it needs a value for that parameter. It doesn’t mean that the parameter can’t be null. See Pat’s post. You handle the issue of nulls in the criteria rather than in the parameter. It gets confusing, but the parameter is a property of the query, while the criteria is part of the WHERE or HAVING condition of the SQL.

Reply | Quote

As Patt suggests you can use OR criteria to test for Null values in query criteria. Also using Nz function would be much simpler than using IIf with IsNull. Instead of:

Like IIf(IsNull([Forms]![frmReportPrinting]![txtTaskOrderNumber]),”*”,[Forms]![frmReportPrinting]![txtTaskOrderNumber])

I’d use:

Like Nz(([Forms]![frmReportPrinting]![txtTaskOrderNumber]),”*”)

Explicitly specifying form reference as query parameter is probably best approach, another option would be to wrap expression in Eval function. Example:

Like Eval(“Nz([Forms]![frmReportPrinting]![txtTaskOrderNumber],’*’)”)

If you use this expression, when you open 2nd (crosstab) query based on 1st query you will not get the “Jet database engine does not recognize….” msg even though form reference not explicitly specified as a parameter in 1st query. Note use of double quotes around expression to be evaluated by Eval, & single quotes around asterisk. However, if referenced form is not open when either query opened, the Eval function will result in a somewhat cryptic msgbox, as illustrated.

HTH

Reply | Quote

The Like Nz(([Forms]![frmReportPrinting]![txtTaskOrderNumber]),”*”) worked like a charm.

Thanks!!!

Vernon

Reply | Quote