Below is the list of fixes and improvements in Active Query Builder ASP.NET Edition v.0.2.1.
+ The canvas can be hidden now. Use the "visible" property on control or just delete it from the web page. The new sample project "no_design_area_demo" is added. In conjunction with the new properties of the QueryBuilder component this allows you to build queries by dragging fields from the database objects tree to the columns grid. + The new properties AddLinkedObjects and DeleteUnusedObjects are added to the QueryBuilder.LinkOptions group. The AddLinkedObjects instructs the component to add necessary objects to join the newly added object with existing objects. For example, using the Northwind database, by adding Orders and Products tables to the query, the [Order Details] table will be added automatically and joins will be set according to the foreign keys. The DeleteUnusedObjects property instructs the component to remove objects from the query if their fields are not used in the query and these objects are no longer used to link other objects. - Fixed bug with clearing a query text or removal of all tables from the canvas. + Compatibility with Microsoft Ajax Framework is made. Now the component can be used with UpdatePanel. - Fixed bug with link rendering and creation. - Ability to change join types via the context menu is restored. + The jQuery library is upgraded from 1.7.2 to 1.8.3.
[ Legend: ] [ + New feature ] [ = Improved/changed feature ] [ - Bug fix ] [ ! Important notice ]
You can always get the latest trial version of Active Query Builder ASP.NET Edition at the download page.
We have been using Active Query Builder for over a year and must say that both the product and support have been outstanding!
We chose Active Query Builder due to its flexibility and features, but have been truly pleased by its power and hidden capabilities. ...
In summary Active Query Builder provides excellent components, great support and a very flexible feature set. It has allowed us to provide features to our end users that I did not think would be possible in the first release of our new tools and in a timeframe that was much shorter than planned. I would recommend that anyone dealing with databases in the .Net world should be aware of this component and its capabilities!