Add a new Result field, FieldD=binary(fieldC, 12), and make the
record selection on FieldB=FieldD
However I suppose it is moot, since [from another posting] presumably
the SUBSTR() was used to replace the BINARY().
FWiW, I can not comprehend why anyone ever chose to put that
low-value function in the Query/400, when so many worthwhile functions
remained missing. What possible value to have BINARY() in the Query
Definition, versus having to create a VIEW, like with many other
functions? Does anyone actually use the BINARY() function? If so, for
what purpose?
Regards, Chuck
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
