• Subject: Re: Mixed Case Keys
  • From: Bob Larkin <blarkin@xxxxxx>
  • Date: Mon, 22 Sep 1997 20:53:10 -0700
  • Organization: Larkin Computer Consulting

boothm@ibm.net wrote:
> 
> on 09/19/97 at 11:31 AM, "Bill Phelps" <phelpswr@alpha.obu.edu> said:
> 
> 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
> 

Ok guys and gals, I think this is the absolute simplest and quickest way
to solve this problem.
            CHGPF (filename) SRCFILE(srcfilelib/srcfile)
SRTSEQ(*langidshr)

Here is a peek at a file before & after using the above statement.
 SRTSEQ(*HEX)            SRTSEQ(*LANGIDSHR)
Record#  MXDKEY         Record#  MXDKEY
      2  a                    1  A     
      4  b                    2  a    
      6  c                    3  B     
      8  d                    4  b     
      1  A                    5  C     
      3  B                    6  c     
      5  C                    7  D     
      7  D                    8  d    

The MXDKEY is a 4 byte char, and is the sole key field in the file.
(Actually it's the only field!)
Pretty simple!
I do not think you will get a level check either! If you did, it
shouldn't be too difficult to recompile the program.
Well... Have I missed something here? 

-- 
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.