Is there a wizard or dialog box component that developer can place on forms (maintenance forms) which the end user can do filter on the primary BO?

i.e. Customer.Zip=33998 or (Customer.Balance>=100 and Customer.Balance<=500).



This way the end user can go thru a wizard or dialog to select the fields, assign operators and values, and then the component can generate SQL command for data access?



Is there such a component available or in the pipeline?



Thanks!

..ßen

No, we don't have such a component.  Several of the control vendors have a filtering system built into their grids, but we don't have one.  As for the filtering mechanisms built into grids like Infragistics and DevExpress, they only filter their internal rows collection; they don't use the Filter property of the IBindingListView (which wraps the BO's filter method).

Ben, the new DX 2007.1 edition of their grid, uses their XPO backend for filtering and sorting (Server side, rather than the old way of doing it in the grid). Which means, the grid is making filter requests to XPO for results. However, I wonder if that relationship is only tied to XPO or other ORM can be used (i.e. SF)? Secondly, I think the grid is making request to XPO via proprietary filtering syntax of XPO rather straight SQL commands.



Secondly, it seems like the Match Orcas CTP has had a major improvement over LINQ and Entity Modeling. Will you guys take advantage of this to provide some visual way for end user to build query/filter?

..ßen

Hey Ben,

There are several decisions that you are going to have to make as you move forward.  If time frames and a solid development environment are desired, then let me give a bit of warning from experience....stay away from developing production apps with CTP technology .  Though the CTPs are a great tool for development shops like ourselves who create developer tools because it allows us to create product before release.  However, this is also a major downside as well.  As we have previously discovered developing on CTP platforms, we have to change roughly 20% of our code base once the final release is ready due to continuing development on the Microsoft side.

My point is that though it is nice to see and play with the new technology it can also dramatically cut into your productivity.

As we have discussed before, we will provide full support for LINQ and a true object entity model once this is avaialble which will by its very nature bring some new controls to the table such as Query and Filter controls.  However, until then we will not release any CTP level controls due to the nature of developing on a CTP platform which ultimately produces many more production and support issues.

Thanks Trent for the well pointed advice!

Before getting too wrapped up with current technology for creating "filtered Dialog", I just wanted to explore the possibility of LINQ bringing that functionality in the future!



I guess we just have to wait and see how stable LINQ is becoming!



Thanks!

..ßen

LINQ is a great technology that we are very excited to incorporate....however, experience has definitely taught us that taking the side of caution on introducing this type of technology is definitely the most prudent decision. 

There will always be a new technology that is coming out....after LINQ it will just be something else.  At some point in the world of production development, we all have to go with what is available....otherwise we will never have a product to distribute