I am in the process of converting from D3.  I am finding that there is
a couple of files that have Upper/Lower case data in them as well
upper case (You have to love consistency).  I am lucky in that I have
asked and been told that there should be only 2 places this should be
a problem.

The dictionary just points to the attribute - it does not do a MCU on
it.  This creates the problem that they have data in there like,
mcclure,Mcclure,MCCLURE.

I have modified the dictionary item to do a MCU on it.  I have the
files set up to to NO.CASE so that any keys will not have a problem
with the case however, I know of no way other than what I just did to
handle the data.

How are others handling that situation?

Eugene

Hi again Eugene,

There are three case sensitivity mechanisms that may be of interest.

1. Case insensitive record ids

I don't think this is relevant to your problem but is worthy of a
quick
discussion anyway.

The QM file system uses case insensitive record ids by default except
for
directory files where case sensitivity depends on the underlying
operating
system. For hashed files, there is an option to choose case
insensitivity in
which case records with ids AA, aa, Aa and aA are all the same.

2. Case insensitivity in the query processor

The query processor is case sensitive by default. The various
operators used
in a selection clause all support the NO.CASE option, for example
   LIST CUSTOMERS WITH NAME LIKE NO.CASE "Mr..."
or
   LIST VOC WITH TYPE EQ NO.CASE "v"

Note that our implementation truly is case insensitive unlike the
unusable
version recently added to UniVerse where it simply translates what you
type
to upper case and compares with the data as stored in the record. The
first
example above would find "MR JONES" but not "Mr Jones". (I have moaned
to
IBM who admitted that it does seem to be wrong).

The OPTION QUERY.NO.CASE command can be used to make the query
processor
case insensitive by default.

3. Case insensitivity in QMBasic

The $NOCASE.STRINGS compiler directive (or its equivalent in the
$BASIC.OPTIONS record) can be used to make string comparisons case
insensitive.

Martin Phillips
Ladybridge Systems Ltd
17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB
+44-(0)1604-709200

thanks for that explanation Martin.
clears up some questions in my mind as well.
i'll hang on to this email for future reference.
 
Steve Trimble
Computerized Data Mgmt Inc
PO Box 13403
Maumelle, AR 72113
(501) 803-0974 09:00am - 6:00pm CST
 
Home of self defense products: http://www.protecturself.com