![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 11 to 12 of 12 total |
![]() |
Mon, May 18 2009 5:21 PM | Permanent Link |
"Rita" | "Sean" <SeanNotLikeSpam@fakeisp.net> wrote in message news:BCCFAD3C-A65E-4DB7-B307-15969DE11E3F@news.elevatesoft.com... > > Index the table by the key you are looking for. Start at the first record > & get your first distinct value. Thinking down them roads great minds and all ![]() >Do what you want with it. Change the last character in the distinct value >to the next ordinal value. For example, 'Jones' would become 'Jonet'. Do a >find nearest on this value to get the next distinct key value. Repeat until >no more are found. Probably not necessary for text data, but you could be >safe and check for a string ending in a character 127 or 255 and in that >case append a CHR(1) instead of changing the last character. Sean thats oneway but now my grey cells are thinking on overtime and a logical field true for the 1st distinct of each name and false thereafter would be a breeze really thanks for that kick in the rear. Rita |
Tue, May 19 2009 3:19 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Rita
>Sean thats oneway but now my grey cells are thinking on overtime and >a logical field true for the 1st distinct of each name and false thereafter >would be a breeze really thanks for that kick in the rear. Or maintain a separate table of unique names. Even faster for lookup Roy Lambert [Team Elevate] |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |