>> Well this works. But it doesn't look veriy logical to me, as products has be >> defined to be a sql-databse table. >> >Not true. The default is for GDBM files. If you need to search >against an SQL server then you must specify the non-default search >type. Maybe I have to learn more "interchange thinking'. I thought, when I define products in catalog.cfg to be a sql-database table, this would be valid for all components. >> code: >> ========= < >> form action="[area search]" method=post> >> Suche:<br> >> <!-- code doesn't work --> >> 1 [set testname]su=yes/sf=description/st=db[/set] >> 2 <input type=hidden name=mv_profile value=testname> >> 3 <input type=text name=mv_searchspec size=15 value=""> >> >> <!-- code works >> 4 <INPUT TYPE=hidden NAME=mv_searchtype VALUE=db> >> 5 <INPUT TYPE=hidden NAME=mv_search_field VALUE="description"> >> 6 <input type=hidden NAME=mv_substring_match value=1> >> 7 <INPUT type=text NAME=mv_searchspec size=15> >> --> >> >> </form>============== >> >Correct. What do mean with correct? I wanted to know, why lines 1-3 don't work. Well, I've got a solution for this problem, see other posting. Rolf Schaufelberger suppressed _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.