Thanks alot for that-will try today,I can confirm they have paid up so
far-which has been 3 times ,so am unsure why now they are not replying.

Hi Jay,

I have to put my hands up and admit that's a common complaint.

To fix this I would need to completely redesign my search algorithm as
the current algorithm makes it too expensive for me to count the number
of remaining database entries for each alternative option in an already
selected list. The reason the problem exists at all is that I want the
lists to dynamically update as options are selected by the user
(assuming javascript is turned on, that is) - that way users are never
taken down a blind alley to an empty search result.

(NOTE: non javascript users are still given the option to compile their
entire set of requirements and then hit "go" although this can result in
a null result)

If I dropped the dynamic update requirement then the solution to this
problem would be simple but the user complaints would be of a different
nature (namely, "I keep wasting my time with invalid searches. Can you
not remove options that don't apply?").

Anyway, improving the search mechanism is definitely on my to do list
but with so much more immediate work building up (and a database that
still requires largely manual data maintenance on a continual basis) it
may be a while before I get there.

For now you'll just have to select "ANY" again to get the original list
to reappear - cumbersome, I know, but much as I really want to fix this
problem (I'm in full agreement with your frustration) there's not a lot
I can do about it right now. Believe me...it's as frustrating for me as
it is for you.

Such are the problems when there's just one of you to do the work of
many. I'm amazed I've managed thus far!

Of course...if anyone can point me in the direction of any useful
literature on the subject of efficient web search algorithms that may be
relevant to my problem I may be able to get there a little faster.

cheers,
Reestit Mutton