Hi Sergio,
I've add a new type of filter to dbforms's capability, an sql filter that is simply an SQL condition, passed as a DbFormTag's attribute. This
type of filter is much better than the old one, but the coding changes are rilevant, so I post here the diff, and we can discuss about it pros and cons and decide what to do. In bookstore examples there is an application of filtering, in master and child forms.
Good idea, but i would prefer a backward compatible mode. I think a new attribute like SQLFilter would be better solution. I think there are lot of applications outside the world wich work with the old filter and where attributes and i do not like to break the compatiblity.
I have not looked detailed at your changes - the diffs are very difficult to read...
Could you explain which files are needed to be changed and what you have done...
The problem to solve is to pass the sqlFilter value from DbFormTag attribute to the code that build up the sql query. To solve I have to change the signature of NavigationEvent's method processEvent, adding a new parameter containing the data. This cause a long sequence of changes.
Is a new attribute possible?yes, I call it "sqlFilter", It has no relation at all with old one.
cheers, Sergio Moretti
------------------------------------------------------- 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
