Problem with INSTR()

[John Esak]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenbrody at bestweb.net]
> Sent: Wednesday, February 15, 2006 10:53 AM
> To: john at valar.com
> Cc: Fplist (E-mail); support at fptech.com
> Subject: RE: Problem with INSTR()
>
>
> Quoting John Esak (Wed, 15 Feb 2006 10:22:04 -0500):
> [...]
> > > You're forgetting that filePro is case-insensitive here.  Using
> > > INSTR() to find "L" will also find "l".
> > >
> >
> > I'll bring this private email to the list.  Yes, I am certainly aware
> > that filePro is case-insensitive when doing compares on an "if" line
> > with "eq" or even "=". However, this is a function call to look for a
> > specific *character*... and little "l" is completely *not* big "L". :-)
>
> Are you sure?
>
>     If:  "l" eq "L"
>   Then:  mesgbox "'l' and 'L' are the same!"
>
> :-)

No, no, no,.... (at the risk of sounding like the bit in Tron... :-))
Sorry, but that is a completely irrational analogy. What I am saying (very
clearly) is that the following would not get the desired results from your
point of view...

    if:  l eq chr("76")
  then: show "Ken is right, John is wrong! :-)";  end
    if:
   then: show "John is right! :-)  -- doesn't happen often, but even a blind
         squirrel gets the nut sometimes."


Truly, I believe if someone specifies a *particular* character with the use
of chr(), filePro should respect that. It does *everywhere* else I have
tried, and I just tried about 10 different things. Why should this INSTR()
function be any different?

Besides, it certainly would give the INSTR() function a lot more depth.

So what would be wrong with PFINSTRWORKSLIKEJOHNWANTSITTO=ON  ??

and keep the default OFF if you must. :-)

John