James,

Thanks for your suggestion. My issue was not with the where clause in the
query, but with the validation in the report's parameters. I don't want the
report to allow both parameters to be null. Also, this report doesn't lend
itself to default values for either of these two parameters.

What I ended up doing was forcing on the the parameters to a string and
setting the default to ' '. This produced an empty report on initial load. If
the user backspaces this value out of the prompt and clicks View Report,
he/she'll get a gazillion records. Oh well. Otherwise, they'll fill in a
valid value for either of the two parameters and get just what they want.

It's not the cleanest solution, but it works.

Thanks,
Barry