> But what's with the idea to support more than one searchfield? The
> select above will not distingish between both fields.
>
Hmm, that is true..
What about extending HashTable by something like:
class newHashTableOrSomethingElse extends java.util.HashTable {
public String get(String fieldname, int num) {
String oldFieldName = (String)super.get(fieldname);
return oldFieldName + ":" + num;
}
}
Declare searchFieldNames, searchFieldModeNames etc of this type.
Old application will still run.
Within a JSP you can now use multiple fields for the same
field by using e.g. :
searchFieldAlgorithmNames_tableName.get("columnName",2)
searchFieldNames_tableName.get("columnName",2)
as fieldNames. So you would know which fields belong together.
Can't oversee implementation consequences at the moment, just
a thought, you surely know better. Would that be possible?
I just would like to have the option of using a separate
operator select, maybe we here cannot imagine, but there are people
out there who do not know operators like '>', '<', '>=' etc.
Regards
Dirk
-------------------------------------------------------
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
