Chris,
The problem is that your index was built case sensitive and now you're requests 
are upper case only so it will only get upper case indexes. You need to rebuild 
the index with the dictionary item that does the MCU, that way all of your 
indexes are upper case.
Hth,
Curt Stewart

Chris Austin <cjausti...@hotmail.com> wrote:

>
>> Could you create another dict item called NAME.UPCASE and put the MCU in 
>> that definition?
>
>I guess I'm not sure what the above dictionary entry would look like. Would 
>this be a dictionary entry
>that's just used to do the conversion on NAME?
>
>Currently this is what I have for field name:
>
>      NAME
>> 0001 D
>> 0002 5
>> 0003 
>> 0004 Name
>> 0005 25L
>> 0006 S
>> 0007
>> 0008 CHARACTER,25
>
>So I would be creating another DICT entry called NAME.UPCASE, the part I don't 
>understand is 
>
>#1) what that DICT would look like
>#2) how that DICT entry would be used
>
>Sorry for the numerous questions. 
>
>Chris
>
>
>
>> From: bl...@shaklee.com
>> To: u2-users@listserver.u2ug.org
>> Date: Tue, 26 Jul 2011 10:41:40 -0700
>> Subject: Re: [U2] CONV MCU on indexed field?
>> 
>> Did you create the index for the field like John Thompson suggested?
>> 
>> -----Original Message-----
>> From: u2-users-boun...@listserver.u2ug.org
>> [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Chris Austin
>> Sent: Tuesday, July 26, 2011 10:37 AM
>> To: u2-users@listserver.u2ug.org
>> Subject: Re: [U2] CONV MCU on indexed field?
>> 
>> 
>> 
>> I changed the DICT entry for field NAME on the CLIENT table to the
>> following:
>> 
>>      NAME
>> 0001 D
>> 0002 5
>> 0003 MCU
>> 0004 Name
>> 0005 25L
>> 0006 S
>> 0007
>> 0008 CHARACTER,25
>> 
>> But it still doesn't seem to work in regards to the case-sensitive.
>> 
>> Chris
>> 
>> 
>> 
>> > From: bl...@shaklee.com
>> > To: u2-users@listserver.u2ug.org
>> > Date: Tue, 26 Jul 2011 09:44:35 -0700
>> > Subject: Re: [U2] CONV MCU on indexed field?
>> > 
>> > We are using Unidata and this is a dict for Country:
>> > 
>> > CNTRY:
>> > 
>> > D
>> > 
>> > 4
>> > 
>> > MCU
>> > 
>> > Cntry
>> > 
>> > 6L
>> > 
>> > M
>> > 
>> > 
>> > You could do the same change to the NAME definition but I was 
>> > suggesting that if you didn't want to or couldn't do that then another 
>> > definition could be created that forced the name to be upper-case.
>> > 
>> > -----Original Message-----
>> > From: u2-users-boun...@listserver.u2ug.org
>> > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Chris 
>> > Austin
>> > Sent: Tuesday, July 26, 2011 9:36 AM
>> > To: u2-users@listserver.u2ug.org
>> > Subject: Re: [U2] CONV MCU on indexed field?
>> > 
>> > 
>> > 
>> > I'm not exactly following you. Would this dict item called 
>> > NAME.UPCASE, would that be a new field to test this or woudl that be a 
>> > specific field used to do the conversion? What would the dictionary 
>> > look like.
>> > 
>> > Chris
>> > 
>> > 
>> > > From: bl...@shaklee.com
>> > > To: u2-users@listserver.u2ug.org
>> > > Date: Tue, 26 Jul 2011 09:32:48 -0700
>> > > Subject: Re: [U2] CONV MCU on indexed field?
>> > > 
>> > > Could you create another dict item called NAME.UPCASE and put the 
>> > > MCU
>> > > in that definition?
>> > > 
>> > > -----Original Message-----
>> > > From: u2-users-boun...@listserver.u2ug.org
>> > > [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Chris
>> > > Austin
>> > > Sent: Tuesday, July 26, 2011 9:25 AM
>> > > To: u2-users@listserver.u2ug.org
>> > > Subject: [U2] CONV MCU on indexed field?
>> > > 
>> > > 
>> > > 
>> > > We've been using the following command to select a name regardless 
>> > > of
>> > > how it's capitalized:
>> > > 
>> > > SELECT CLIENT WITH NAME CONV MCU = "BRUCE]"
>> > > 
>> > > However, after I indexed the field NAME on the CLIENT table the same
>> > > command only returns the values that match the case-sensitive. In 
>> > > other words after we indexed the field name it doesn't seem that we 
>> > > can use CONV MCU, is there a work around to this?
>> > > 
>> > > Thanks,
>> > > 
>> > > Chris
>> > > 
>> > >                                            
>> > > _______________________________________________
>> > > U2-Users mailing list
>> > > U2-Users@listserver.u2ug.org
>> > > http://listserver.u2ug.org/mailman/listinfo/u2-users
>> > > _______________________________________________
>> > > U2-Users mailing list
>> > > U2-Users@listserver.u2ug.org 
>> > > http://listserver.u2ug.org/mailman/listinfo/u2-users
>> >                                      
>> > _______________________________________________
>> > U2-Users mailing list
>> > U2-Users@listserver.u2ug.org 
>> > http://listserver.u2ug.org/mailman/listinfo/u2-users
>> > _______________________________________________
>> > U2-Users mailing list
>> > U2-Users@listserver.u2ug.org 
>> > http://listserver.u2ug.org/mailman/listinfo/u2-users
>>                                        
>> _______________________________________________
>> U2-Users mailing list
>> U2-Users@listserver.u2ug.org
>> http://listserver.u2ug.org/mailman/listinfo/u2-users
>> _______________________________________________
>> U2-Users mailing list
>> U2-Users@listserver.u2ug.org
>> http://listserver.u2ug.org/mailman/listinfo/u2-users
>                                         
>_______________________________________________
>U2-Users mailing list
>U2-Users@listserver.u2ug.org
>http://listserver.u2ug.org/mailman/listinfo/u2-users
>
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to