C
Clif McIrvin
I created my first search form last week; and in today's thread "Using
only one record" Allen Browne offered his sample search form:
Here's an example of how to make a search form:
Search form - Handle many optional criteria
at:
http://allenbrowne.com/ser-62.html
It involves writing some VBA code to create the Filter string. It's
worth
spending half an hour to download the example and see how it works, as
you
will use this approach in many other contexts as well.
-----------
In the process of crafting my search form, I stumbled across (A2003) the
BuildCriteria function. I notice that Allen's example doesn't use it,
and I can think of at least two possible explanations:
1. Allen's code predates the BuildCriteria function (or)
2. By avoiding BuildCriteria you (the developer) retain control over
precisely what your code is doing.
The question: Should I avoid, or use, BuildCriteria?
only one record" Allen Browne offered his sample search form:
Here's an example of how to make a search form:
Search form - Handle many optional criteria
at:
http://allenbrowne.com/ser-62.html
It involves writing some VBA code to create the Filter string. It's
worth
spending half an hour to download the example and see how it works, as
you
will use this approach in many other contexts as well.
-----------
In the process of crafting my search form, I stumbled across (A2003) the
BuildCriteria function. I notice that Allen's example doesn't use it,
and I can think of at least two possible explanations:
1. Allen's code predates the BuildCriteria function (or)
2. By avoiding BuildCriteria you (the developer) retain control over
precisely what your code is doing.
The question: Should I avoid, or use, BuildCriteria?