That is up to you. Try rebuilding the index on "NAME" and see what that gets
you.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Chris Austin
Sent: Tuesday, July 26, 2011 10:51 AM
To: [email protected]
Subject: Re: [U2] CONV MCU on indexed field?



Basically what I tried was editing the existing DICT entry for the field
NAME, by placing the value MCU in line #3. I don't think this is what John
referred to though. Should I keep the field NAME like it is now (without the
MCU) and create another DICT entry? 

Chris

> From: [email protected]
> To: [email protected]
> 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: [email protected]
> [mailto:[email protected]] On Behalf Of Chris 
> Austin
> Sent: Tuesday, July 26, 2011 10:37 AM
> To: [email protected]
> 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: [email protected]
> > To: [email protected]
> > 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: [email protected]
> > [mailto:[email protected]] On Behalf Of Chris
> > Austin
> > Sent: Tuesday, July 26, 2011 9:36 AM
> > To: [email protected]
> > 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: [email protected]
> > > To: [email protected]
> > > 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: [email protected]
> > > [mailto:[email protected]] On Behalf Of Chris 
> > > Austin
> > > Sent: Tuesday, July 26, 2011 9:25 AM
> > > To: [email protected]
> > > 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
> > > [email protected] 
> > > http://listserver.u2ug.org/mailman/listinfo/u2-users
> > > _______________________________________________
> > > U2-Users mailing list
> > > [email protected]
> > > http://listserver.u2ug.org/mailman/listinfo/u2-users
> >                                       
> > _______________________________________________
> > U2-Users mailing list
> > [email protected]
> > http://listserver.u2ug.org/mailman/listinfo/u2-users
> > _______________________________________________
> > U2-Users mailing list
> > [email protected] 
> > http://listserver.u2ug.org/mailman/listinfo/u2-users
>                                         
> _______________________________________________
> U2-Users mailing list
> [email protected] 
> http://listserver.u2ug.org/mailman/listinfo/u2-users
> _______________________________________________
> U2-Users mailing list
> [email protected] 
> http://listserver.u2ug.org/mailman/listinfo/u2-users
                                          
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users

Reply via email to