Hi,

last night I tried to compare the efficiency of FindWiz and of
Tamoggemon's FileFind (which also searches cards, but - on the plus
side - lets you easily choose where to search, and - on the minus side
- can only look inside .txt files).

I put a small text file with the string xxyyzz into three different
folders on my card.
I then set both progs to work.

-FindWiz: I called up the well hidden option to select file types,
unticked everything but .txt, waited six minutes while the card was
scanned...
then FindWiz took 1 min 36 s to scan 16,000 records and find the three
files.

-FileFind, if simply given the string, took 11 min 12 s to find the
three files; if told to look only for files with names ending on .txt,
the search procedure took 38 s (no delay before the search started).

So, there's room for improvement in FindWiz's search algorithm, BUT,
as long as you can tell it sufficiently precisely what to look for,
it's doing all right.

Therefore, once again: I think the user interface ought to be made
more efficient (It really bugs me, for example, that to select "Search
all cards" I have to scroll through 25 screens of databases in RAM,
and that I can't even program a button to show that option, because
the next time the card is OFF, the button loses its setting and stays
blank even after the card is ON again.).

For interest's sake, I set FindWiz to also look at .pdb files, waited
the customary six minutes for it to scan the card (cheekily decribed
in Help as "a few seconds if you've got many files on your card" or
something like it), then watched it search for half an hour or so: it
apparently looked into every .pdb file containing data, including my
various Bible versions and a 12 volume (in printed form) encyclopedia.

So, if a simple front end for selecting which folders to search should
be hard to install, how about an option to look only at files with a
certain Creator ID (or even a list of IDs)?

Kind Regards,

Jochen