this is the correct way, but now you don't have the limitation of the old filter, and you can write condition like:
this filter is much simple than the old one, but much more powerful. In it you simply write a sql condition, that will be inserted AS IT IS (obviously and-ed with the others conditions generated) in the where clause
Just to be clear, 1) what do I need to enter? WHERE supplier_name like 'Hew%';
or
supplier_name like 'Hew%';
supplier_name in (select supplier_name from suppliers_from_east where supplier_distance < 1000) or supplier_confidence > 100
2) does it work with existing filter attributes (AND-ed to them)? Seems redundant but...yes
it's just a piece of sql code attached to where clause generated, all other parts, like order clause are running indipendently.
3) does it have limitation like can't used with sorting or anything? In other words, if I set it to sort my supplier_name and then the have a user sort that chooses date for example, will everything be peachy and work like a nice cool day in the middle of a scorching hot summer.
sure it is
Or could we tell users, this is a better way to do
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ DbForms Mailing List
http://www.wap-force.net/dbforms
