browse keys (@bk)

[Mike Schwartz-PC Support & Services]

> "Jay R. Ashworth" wrote:
> 
> You know, *just once*, I'd love to hear "well, that was probably not
> the best way we could have {defined,implemented} that, but we're stuck
> with it 40 MLOC later."

	There are probably some times when that was said.  I've heard fPtech
people say "probably not the best way" about some programming concepts at a
convention, but I don't know if they have ever put those comments into print
into print.  (That's another reason why you should attend a full convention
some time... <grin>)

	However, this is NOT one of those times.  For most of the
programming I've done, I *prefer* that equals and some of the other
functions are *not* case sensitive.  It gets really tedious to have to check
all the upper and lower case combinations for most data entry work.  It is
equally tedious to have to apply an allup or other edit type to 99% of the
data fields where I need to do compares.

 	It seems much more logical to me that filePro has the tools to make
the compares case sensitive where they are needed, such as in writing user
defined password routines.

	So, as far as being "stuck" with something that you are implying was
a bad decision 40 years ago, I would have to reply that I hope filePro would
be designed just that same way if it were being redesigned from scratch
today.

Mike Schwartz