Re: SEARCH TWO FIELDS-MATCH BOTH



Then put the criteria on the same row in the design grid to create and "AND"
condition. Separate rows create "OR" conditions.

--
Rick B



"Jan via AccessMonster.com" <u4496@uwe> wrote in message
news:5f77287ef7f49@xxxxxx
In the query criteria of field Description1 I have Like [Enter
Description
1] & "*" and stepped down in the OR criteria for Description2 I have Like
[Enter Description 2] & "*". The user needs to be able to "global" search
the fields but as I have the criteria set it seems to list "either/Or" .
I
want it to find only records that match Description1 and Description2.
Example: If the user enters "Pencil" then "Red" I only want records that
have Pencil in the first description field AND Red in the second.

I've search the query threads but have not found this example requested
yet.

Thanks

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-queries/200604/1


.



Relevant Pages

  • Re: set criteria for several fields
    ... put the criteria on SEPARATE ROWS in the grid. ... >> Rick B ...
    (microsoft.public.access.queries)
  • Re: Query....Queries!
    ... working with test data where all 4 options fields had data. ... Criteria: ... criteria on separate rows put the criteria all on the same ... FIELD 2 CUSTOMER NAME ...
    (microsoft.public.access.queries)
  • Re: Date in criteria not processing all date records
    ... I have a criteria set as <date-180 ... I am trying to find out from this query is the date in date field one ... dropping relevant records. ... criteria need to be on separate rows. ...
    (comp.databases.ms-access)
  • Re: Query....Queries!
    ... Assuming that you are looking for a match if ANY one of the fields matches ... Criteria: ... criteria on separate rows put the criteria all on the same ... FIELD 2 CUSTOMER NAME ...
    (microsoft.public.access.queries)
  • Re: Query....Queries!
    ... "John Spencer" wrote: ... Criteria: ... criteria on separate rows put the criteria all on the same ... FIELD 2 CUSTOMER NAME ...
    (microsoft.public.access.queries)