simple comparison failing

[Tyler]

Odd...my reply to Ken cc'd the list.  I wonder why it showed up so late?

Anyway, 'r' is undefined.  It doesn't have a type, numeric or
otherwise.  So where is ".0" coming from?

r is initially assigned an empty string: r="".  Later on it happens to
have (in this case) a zero plunked in it.  Since I don't know the
datatype that is being passed or the length of the value going into r,
not declaring the type or length seemed reasonable.  Is filepro
casting the value to a type behind the scenes, then?  If so, I would
have thought it would convert it to the same type as the comparison
value (in this case, a string: "Y").

Sorry for any confusion about 'passed in'...I know filePro has global
variable scope within a processing table, but when I write code I keep
a fairly rigid seperation between variables used by subroutines and
those for the main body.  So r isn't really being passed in from
anywhere, I just think of it that way.  All processing is in a single
table, with a bunch of subroutines.