|
Scott Cornell wrote: > > >>> "Bill Phelps" <phelpswr@alpha.obu.edu> > 09/19/97 01:31pm >>> > I have a physical file with a name field > containing mixed case > letters. I would like to use the name as a > key field. On my > programs I always provide an input field to > position the list. > User's have a difficult time getting the > name keyed in the exact > upper/lower case to position the list > correctly. What are some ways > to design a logical file or the application > to ignore the case and > position the list correctly. > > Thanks in advance.... > > ------------------ > > I haven't done anything like this in a > long time, but I think you can do what you > want in Query by tweaking translation > tables and CCSID's (is that the right > acronym?) - maybe the same thing is > possible w/a LF > > HTH > > Scott Cornell > Mercy Information Systems > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". > | To unsubscribe from this list send email to MAJORDOMO@midrange.com > | and specify 'unsubscribe MIDRANGE-L' in the body of your message. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- Look at the LANGID and SRTSEQ parameters on CRTPF. If you specify *LANGIDSHR on the SRCSEQ, you can select a Language ID that places eual weights on both the uper and lower cas of each character. -- Bob Larkin Larkin Computer Consulting blarkin@wt.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | 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.