jaitken0308
Registered User.
- Local time
- Today, 02:31
- Joined
- Jan 23, 2014
- Messages
- 30
No. No.
I would imagine that none of your criteria for selection were bound to any fields in any table.If they were you would be changing them every time someone changed the criteria.
You can use fields as "unbound" just by not setting a control source for them. They will still function in the same way but won't store any data.
The reason for using a combobox, instead of the checkbox, is that a checkbox can either be True or False. So you will find records which are either True OR False.
But what happens if you don't want to include it in the criteria at all?
The combo box with the "N/A" allows for the user to choose not select based on the value in the checkbox.
Another question...
I have my form set up to return the results from these multi-criteria searches on the form itself (the same form you were helping with above). So sometimes, there may be 100s of results to flip through using the next button. I also am adding in a report feature for this, using a query to take the data from the boxes on the form, search the db, return the results, then build a report from it.
Randomly, though, it returns a different number of results than the form search does. For example, I may do a search and choose to return it on the form and get 153 results, but if I use the same criteria and choose to return it in the query I built, I may get 149 results. From what I can see, there is no real reason it should be doing this. There is nothing special about the ones that don't show up in the other search.
In the criteria line of my query, I used the following syntax:
Code:
Like "*" & [Forms]![MyForm]![MyField] & "*"
Any ideas as to why one search returns a different number of results than another search when they both use the same criteria?