huh? i don't do any kind of conversion and it works perfectly well for me.
and sure enough, looking at the OS3.0 ROM source code, FindStrInStr
effectively does the conversion for me. maybe this is something that's
required on OS2.0 or earlier, but i don't think i ever had a problem with
that on OS2.0 either.
there is no strToSearch string in FindParams. do you mean strToFind? at
least on OS3.0 and higher, it should be perfectly safe to use strAsTyped
instead.
however, i think if strToFind contains some bogus string, that indicates
something's going wrong outside the control of your app (assuming you aren't
building up a FindParams struct on your own -- are you?).
----- Original Message -----
From: Bozidar Benc <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 03, 1999 1:13 PM
Subject: RE: FindStrInStr returns always FALSE?
> You must convert the actual string (strAsTyped):
>
> BytePtr convTab = GetCharCaselessValue();
>
> for (z=0; strAsTyped[z] != 0; z++)
> strToSearch[z] = convTab[strAsTyped[z]];
>
> found = FindStrInStr(yourTxtP, strToSearch, (Word *)&fldPos);
>
> Regards
>
> Bozidar
>
>
>
> > Hi there,
> >
> > I am wondering about the FindStrInStr function. When debugging my
> > Search function, the following strings are being passed to FinStrInStr:
> > rec "123456789" (pointer to DB)
> > pattern "1234"
> > &pos 0
> > Unfortunately FindStrInStr returns FALSE.
> >
> > Another thing: The strToSearch seems to be totaly wrong when peeking
> > into the FindParams structure - strAsTyped is ok. I don't think it's
> > the emulator (d29 FYI) because on the real device Search also
> > yields no match. With FindHack, however, the program crashes.
> >
> > Any clue?
> > Holger Klawitter
> > --
> > Holger Klawitter +49 (0)251 484 0637
> > [EMAIL PROTECTED] http://www.klawitter.de/
> >
> >
>
