It looks like you are doing it in the right order... I wonder if that character limit thing is messing you up in attribute 8? (just a shot in the dark)
Also, what flavor of Universe account are you running? You can find this out by: CT VOC cataloged.program.name Look in attribute 6 and it will tell you. That CONV query feature might not work all that well in a PICK flavor account on an indexed field? If all else fails... you can do a work around in BASIC (if this is in a BASIC program) Using OCONV() UPCASE() OR Try the previous posters I type suggestion and see if that works. On Tue, Jul 26, 2011 at 2:38 PM, Chris Austin <[email protected]>wrote: > > Curt, > > I deleted the index completely (DELETE.INDEX CLIENT NAME). > > Then I created the DICT for NAME: > > NAME > 0001 D > 0002 5 > 0003 MCU > 0004 Name > 0005 25L > 0006 S > 0007 > 0008 CHARACTER,25 > > Then I created the INDEX for NAME (CREATE.INDEX CLIENT NAME) > > Finally I built the indices for NAME (BUILD.INDEX CLIENT NAME) > > I then tried to to SELECT CLIENT WITH NAME CONV MCU = "BRUCE]" and only > return 1 value (with all caps) instead of about 152. > > Does the order I'm doing everything appear ok? I'm not sure how to validate > the indexes are in upper case, does anyone know how to validate that? > And when you refer to rebuilding the index using upper case I assume you > mean putting the MCU in the DICT on CLIENT and then doing the > CREATE.INDEX/BUILD.INDEX? > > Chris > > > > > Date: Tue, 26 Jul 2011 13:27:14 -0500 > > From: [email protected] > > To: [email protected] > > Subject: Re: [U2] CONV MCU on indexed field? > > > > 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 <[email protected]> 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: [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 > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > -- John Thompson _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
