RE: multiple search arguments in one scan?

You were the only one that thought so, Rob!  <g>

The primary reason I'm not using it, like Steve Landess pointed out, is that
using LIKE on a string that does not contain any wildcards does not return
any results.  But now I see why.  I didn't pick up on the importance of the
trailing blanks when using LIKE but not when using the equal sign until just
now.

Testing just a bit more.  Finding that I still need to use LIKE or '='
depending on the situation:

 When testing for NAME = 'BALE, DAN       ',

  NAME LIKE 'BALE, DAN%      '  does *not* find record
  NAME LIKE 'BALE, DAN%'        *does* find record
  NAME LIKE 'BALE, DAN'         does *not* find record
  NAME LIKE 'BALE, DAN       '  *does* find record

So, I either need to finagle the ending quote, or I need to change the
predicate.  Probably just easier to change the predicate based on whether
the scan finds a wildcard.

Or am I still not getting it?

db

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx / rob@xxxxxxxxx
> Sent: Tuesday, October 05, 2004 4:24 PM
>
> Hey, I thought my test results showed you that it doesn't matter if you
> use like or =.
>
> Rob Berendt