| Abe Jimenez 2006-07-26, 6:55 pm |
| Actually you can make this work. What you need is to automate the process.
I would add a BeforeAdd and a BeforeUpdate trigger to the file to
automatically build the sorter field from the word field. All you need is a
loop that will read each character in the word and replace it if necesary.
For example:
FIL:Sorter = ''
Loop I# = 1 to Len(Clip(FIL:Word)) by 1
Case FIL:Word[I#]
Of ä
Fil:Sorter = Clip(FIL:Sorter) & 'a'
Of ..... !Create one of these for each letter you want to replace
Else
FIL:Sorter = Clip(FIL:Sorter) & FIL:Word[I#]
End
End
--
Regards,
Abe Jimenez
"Gerd" <schmittinger@unitech.co.za> wrote in message
news:1153824881.767819.166910@h48g2000cwc.googlegroups.com...
Thank you for the suggestion. Unfortunately it will not work since
those Umlauts are all over (also inside the words) and to make these
type of changes about 10,000 times, with new words being added
continuously it will be an impossible task.
Paul S. Person wrote:
> On 24 Jul 2006 06:15:08 -0700, "Gerd" <schmittinger@unitech.co.za>
> wrote:
>
>
> This may not be at all what you want, but it works for me ...
>
> I have a database which includes the titles of maps (Fritsch
> Wanderkarten 1:50.000) purchased when I was stationed in Germany 30
> years ago; some of the titles include umlauted vowels. What I did was
> to create a separate field, called "Sorter", in which I put the titles
> without the umlauts. Thus
>
> Sorter Word
> Arbeit Arbeit
> argern ärgern
> Axt Axt
>
> You then use Sorter as your Key Field but display Word (or whatever
> you call that field) for the user to see. This will solve the problem
> stated, but may or may not satisfy any other requirements you may
> have. Searching a browse box with an incremental locator, for example,
> would have to be done ignoring the umlauts, which may or may not be
> acceptable.
> --
> "I find that a great many things which have been conclusively
> demonstrated by the Ancients are unintelligible to the
> bulk of the Moderns owing to their ignorance"
|