Browse & @bk

[GCC Consulting]

As the original programmer, in this case, I had done upper and  lower case with
@bk as at first, I wasn't not aware that it was not case sensitive.

Even after Ken or Ernie, some time ago, advised me it wasn't necessary, I have
found it hard to break an old habit.

Also, who knows, maybe in release 7.0 of fp, @bk may be case sensitive.  My code
will be prepared. :).

I have changed some browse coding where the use of a lot of variables (letters)
has made the browse structure too long.

As for = vs eq on the if line, again habit; although some my consider it poor
programming.

Since this has cause a new thread, I have to assume that the browse code was
read and understood. Using = vs eq is a matter of syntax which is acceptable to
fp.  I have not run into any program problems in doing so.

As for error checking, the results will be the same.  About the only difference
would be when looking for math function, when using = only for math functions,
and other comparisons using eq.  This may be faster, but one can find math
operations by searching for + - * / operators also.

Since I have gotten into the habit of using field names when doing math, it is
very easy to find any formula which may be creating problems.  

	Total_amount=quantity*price is easy to search for.  I can also look for
a calculations where price appears very simply.  It is quite clear what the
meaning is. 

	if:cd = cust_code			if: cd eq cust_code
     then: GOTO do_this		    then: GOTO do_this

Both codes are clear as to meaning. No one will assume a math function in either
case.

Richard Kreiss
GCC Consulting