Wouldn't it be possible, Eliot, to use all of DBman's search controls, while at the same time utilizing search.cgi's boolean search?
If you write up a html file to make the calls, that is...
<INPUT TYPE="TEXT" NAME="keyword" size=38 maxlength=255> Keyword search
<input TYPE="SUBMIT" NAME="view_records" VALUE="GO!">
</FORM></P>
<P>FORM ACTION="search.cgi" METHOD="GET">
<INPUT TYPE="TEXT" NAME="keyword" size=38 maxlength=255> Boolean search (and/or)
<input TYPE="SUBMIT" NAME="view_records" VALUE="GO!">
</FORM></P>
Of course the above could be modified to do any other sort of dbman search (whole words, reg. exp., etc.) I don't think that's the correct syntax for search.cgi, but you get the idea.
That way, on the same page, you could make calls to both db.cgi search patterns as well as search.cgi search patterns.
Would that work? Or am I dreaming?
------------------
----------------------------------------
Lee Leisure
HP Customer Relations Manager
----------------------------------------
* NOTE: This message is intended
for personal purposes only, and does
not imply the position or opinion of
the Hewlett Packard Company.
If you write up a html file to make the calls, that is...
Code:
<P><FORM ACTION="db.cgi" METHOD="GET"> <INPUT TYPE="TEXT" NAME="keyword" size=38 maxlength=255> Keyword search
<input TYPE="SUBMIT" NAME="view_records" VALUE="GO!">
</FORM></P>
<P>FORM ACTION="search.cgi" METHOD="GET">
<INPUT TYPE="TEXT" NAME="keyword" size=38 maxlength=255> Boolean search (and/or)
<input TYPE="SUBMIT" NAME="view_records" VALUE="GO!">
</FORM></P>
Of course the above could be modified to do any other sort of dbman search (whole words, reg. exp., etc.) I don't think that's the correct syntax for search.cgi, but you get the idea.
That way, on the same page, you could make calls to both db.cgi search patterns as well as search.cgi search patterns.
Would that work? Or am I dreaming?
------------------
----------------------------------------
Lee Leisure
HP Customer Relations Manager
----------------------------------------
* NOTE: This message is intended
for personal purposes only, and does
not imply the position or opinion of
the Hewlett Packard Company.
