|
>I'm trying to provide a case insensitive lookup for a database key field >containing both upper and lower case. The user, by typing: > >FLINTSTONE, FRED > >should be positioned to: > >Flintstone, Fred >Flintstone, Wilma >etc. > >Using the normal collating sequence, this would position beyond all of the F's. >How can this be done without changing the actual data to upper case or creating >an additional field containing the upper case version. > >There must be a simple way to do this... > >Thanks for any help you can provide! > >Glenn Create a logical with a field that translates your field to upper case. There is a DDS keyword to cause the translation and a system table with the lower to upper case translation. Your data remains in mixed case in your physical, but the logical maintains a version translated to upper case. Joe Teff +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.