> > Have you ever tried the build in filter/sorting features in > dbforms? > > They can handle something like this statements. No need to > build own > > filter Tags? Or are they not flexible enough for your > needs? Where is > > the problem with the builtin system? Could we extend the builtin > > system to fit your needs? > > > the tags are about user interaction, not about on how a filter is > applied, anyway, in the new event subsys I could map this in the > whereClause attribute. > For me the problem is not the filter implementation, we can > find a more > clean solution here, but the issue on dbform not fit > by-design against > big tables.
I think we should implement the new sqlFilter feature so that navigation can be can used with the classic navigation. And should maintenance the classic system as far as it could be done. In the moment everything is working with both systems, Except the nice little graying out of the navigation buttons on first and last page. This could only work with the new system. I hope that you could find out how the classic system works internal... If yes please document it. And i think we should document the features and usages of the navigation systems in a chart. Regards, Henner ------------------------------------------------------- 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
