>>I am forming a SQL select for a report on two tables which are in a multiple to multiple
>>relationship (thru a third, cross reference table). (In VFP 5.0a).
>>
>>One list contains equipment and the other (engineering) drawings for the equipment.
>>Each piece of equipment can have more than one drawing and each drawing can be for more than one
>>piece of equipment.
>>
>>When I run the SQL I get drawings assigned to more pieces of equipment than they should.
>>
>>The drawing key is of a form "dr00000v" were "dr" is for drawing and the remaining characters
>>can be any number, upper case or lower case character. Keys are assigned in sequence
>>from a common table as needed.
>>
>>That is "dr000001" , "dr000002" etc.
>>
>>The problem extra drawings occur becuase VFP seems to believe that "dr00000v" and "dr00000V"
>>are equal as well as others where the last character is different only in being a different
>>case.
>>
>>Please try it. When I run the following from the command window I get .T. as a response to
>>? ctemp1 = ctemp2.
>>
>>ctemp1 = "dr00000v"
>>ctemp2 = "dr00000V"
>>? ctemp1 = ctemp2
>>
>>Please, what is happening?
>>
>>It does not help to place "set exact on"
>>
>>It has only happended since yesterday when I loaded version VFP 5.0a. It did not seem to happen
>>under version 5.0.
>>
>>Am I missing something?
>>
>>Best Regards Don
>
>Uh . . . I got .F. for your example. Might want to try using "==" instead of "=" with UPPER() to force comparisons.
>
>Bill

Using == does force a .f. I cannot use UPPER() since I want the upper and lower
case to be a different key.

Is there a "Set equal to approximate" checkbox somewhere that I need to find?

Don