numero = 110501
interpreted = N
texte = > Hi all, >=20 > Trying to build a fairly complex search form for a client. I am = trying to allow the client determine whether a particular search = criteria is required on a field by field basis. >=20 > Is there a parameter similar to 'comp' that I can use to set the = required status for a field. Something like: >=20 > &FIELDNAMErq=3DT >=20 > So in the form code I could have: >=20 > Hi Tim I don't know what you mean by "comp", here ... but to require one of = your [search] comparison parameters, you just put "rq" at the end of the = first part of the parameter.. you must know/remember this ... So if I want the "ROOM" field to be required, then I do ...&eqROOMdatarq=3D[theRoomSearchStringToCompareToData]... If I had done this instead: ...&eqROOMdata=3D[theRoomSearchStringToCompareToData]... ...then that comparison is just one possible reason the search might = find records... depending on what other params you built up. There may be more clever ways of doing what you ask, but if I understand = your need correctly, you could do this: ...&eqROOMdata[isROOMrequired]=3D[theRoomSearchStringToCompareToData]... HTH -Govinda=
Associated Messages, from the most recent to the oldest:
> Hi all, >=20 > Trying to build a fairly complex search form for a client. I am = trying to allow the client determine whether a particular search = criteria is required on a field by field basis. >=20 > Is there a parameter similar to 'comp' that I can use to set the = required status for a field. Something like: >=20 > &FIELDNAMErq=3DT >=20 > So in the form code I could have: >=20 > Hi Tim I don't know what you mean by "comp", here ... but to require one of = your [search] comparison parameters, you just put "rq" at the end of the = first part of the parameter.. you must know/remember this ... So if I want the "ROOM" field to be required, then I do ...&eqROOMdatarq=3D[theRoomSearchStringToCompareToData]... If I had done this instead: ...&eqROOMdata=3D[theRoomSearchStringToCompareToData]... ...then that comparison is just one possible reason the search might = find records... depending on what other params you built up. There may be more clever ways of doing what you ask, but if I understand = your need correctly, you could do this: ...&eqROOMdata[isROOMrequired]=3D[theRoomSearchStringToCompareToData]... HTH -Govinda=
John Butler
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...