>
> Hi Henner,
>
> ...
> >
> > > Currently the 'search algorithm field' allows to select
> between '='
> > and
> > > 'like' queries. That is already the choice of an operator.
> > Yes, but the user do not have a choice.
> Cannot I do something like:
>
> <select name='<%=
> searchFieldAlgorithmNames_tableName.get("columnName") %>'>
> <option value="">Equals
> <option value="weak">is like
> </select>
>
> Isn't current dbforms able to handle that?
> I thought of extending that to
>
> <select name='<%=
> searchFieldAlgorithmNames_tableName.get("columnName") %>'>
> <option value="">Equals
> <option value="weak">is like
> <option value="ne">is not equal
> <option value="lt">is lower than
> ...
> </select>
>
> Wouldn't that be possible? We would not even need a new parameter...
>
Yes, i think this would be possible.
But what's with the idea to support more than one searchfield? The
select above will not distingish between both fields.
Regards,
Henner
-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
DbForms Mailing List
http://www.wap-force.net/dbforms
