Subject | Re: Searching by range |
---|---|
Author | jeffplata |
Post date | 2005-08-18T04:42:49Z |
Hi Jason,
The BETWEEN syntax could easily accomplish my purpose in the original
post, accomodating searches by range. I would like to nudge it a
little more for the sake of the user's convenience. For example,
instead of typing BETWEEN <val1> AND <val2>, or IN(<val1>,<val2>,...),
the user could simply type <val1>-<val2> and <val1>,<val2>,... for the
BETWEEN and IN syntax respectively. That is if there is an event that
fires before the actual search, so that the input criteria can be
parsed and replaced with the correct syntax. I know there is an
aftersearch event of the TIB_Query, but I'm not sure if this fires
before performing the search. My question is, is the aftersearch event
appropriate for this purpose? (Can only test not until midnigt today).
TIA
Jeff
> Also keep in mind, when in search mode you can put IN( val1, val2, val3,Never thought there is so much power in IBO's search mode until now.
> ... ) or BETWEEN val1 AND val2 and it will work just fine.
The BETWEEN syntax could easily accomplish my purpose in the original
post, accomodating searches by range. I would like to nudge it a
little more for the sake of the user's convenience. For example,
instead of typing BETWEEN <val1> AND <val2>, or IN(<val1>,<val2>,...),
the user could simply type <val1>-<val2> and <val1>,<val2>,... for the
BETWEEN and IN syntax respectively. That is if there is an event that
fires before the actual search, so that the input criteria can be
parsed and replaced with the correct syntax. I know there is an
aftersearch event of the TIB_Query, but I'm not sure if this fires
before performing the search. My question is, is the aftersearch event
appropriate for this purpose? (Can only test not until midnigt today).
TIA
Jeff