How to handle multiple null values using form-based parameter queries?

[tim_tims33]

Hi, i'm creating a search form giving the end user a range of controls to use when filtering/searching data. See the image.

But, i think my range search (using the textbox) to put in a lower and upper limit...is preventing this from working. In fact, when i put data into all the controls, no data pops up in my subform. How can i get around this?

My query data source can also be seen...showing you how i've handled teh null entries. (Hmmm..perhaps i need to put in a null 'handler' for the two textboxes??)



Please advise where you can...

Many thanks
tim

[June7]

LIKE operator is only useful with wildcards: LIKE [Forms]![frmSearch]![txtSurnameSearch] & "*"

Is [Member ID] a text or number?

Why are the controls under the [Member ID] field named with 'StartDate' and 'EndDate'?

Is data in each of these fields required?

[Rod]

Hm! First question is: do you expect data in the result set?

I notice in the snapshot of the query grid that you have date comparisons. Date comparisons are often the culprit when getting an empty result set (or an unexpected result set). Here is a link to an explanation about Access dates - far better than I could ever write it.

http://allenbrowne.com/ser-36.html

In fact I would advise you to scan all of Allen's site, it's a cornucopia of information.

Unfortunately we cannot see all of your design grid; try posting the SQL. The second comparison filters by surname. I would tend to write this as (use your own form and control names)

Like Trim(Nz([forms]![form1]![text0],"")) & "*"

I can't comment on the other comparisons as they are hidden.


PS June, you got there first - again!