What! That's not a bug? That sounds kinda crippling to me. What's the point
of having a 'Find' feature if it can't do sub-string searches? It's like
the job is only half done.
I agree, I use FindHack, but still, that's kinda cheesie. I can only assume
that 3Com was trying to maximize cpu cycles since the dragonball processor
is not a speed demon. Since processing power is an issue, this kinda makes
sense <place annoying throat cough here>.
At 11:33 AM 12/2/1999 +0100, you wrote:
>[EMAIL PROTECTED] wrote:
>> If I search (by pressing on the "lense") for "068" it wont find any record
>> although 068 is in the second number. If I search for 89 the second
record will
>> be found. If I look for "50" both numbers are found. It seems, that palm
finds
>> all records *beginning* with the search-string but not *containing* the
>> search-string.
>
>It's not a bug:
>
>Palm III Handbook (english version), Page 63:
> Find locates any words that begin with the text you enter. For
> example, searching for "plane" finds "planet," but not "air-
> plane."
>
>That's why FindHack is so useful (not because of the sisssy regexp stuff :-)
>
>Regards,
> Holger Klawitter
>--
>Holger Klawitter +49 (0)251 484 0637
>[EMAIL PROTECTED] http://www.klawitter.de/
>
>
>
Allen Shymchuk
http://www.asynccomputing.com/
