Downloads » Active Query Builder 2 ASP.NET Edition History
Below is the list of fixes and improvements in Active Query Builder 2 ASP.NET Edition v.2.12.0.
+ Ability to restore the component's state after session expiration without reloading the page has been made. = Ping action now detects session expiration. + Overlay to disable visual UI controls is made. The new functions are added to show/hide the overlay: QB.Web.Application.showOverlay(message), QB.Web.Application.hideOverlay(). + New functions are added to set and clear the filter for the Database Schema Tree: QB.Web.Application.TreeComponent.setFilter(filter), QB.Web.Application.TreeComponent.clearFilter(). - The bug with not displaying fields if object added twice to the canvas has been fixed. - The procedure parameters dialog was displayed incorrectly using the old database schema control. Fixed now. - The bug with incorrect displaying of objects in the old schema tree control in MVC projects is fixed. - A memory leak while using the control in "Multiple Queries Per Session" mode has been eliminated.
[ Legend: ] [ + New feature ] [ = Improved/changed feature ] [ - Bug fix ] [ ! Important notice ]
You can always get the latest trial version of Active Query Builder 2 ASP.NET Edition at the download page.
Active Query Builder WinForms .NET Edition:
Active Query Builder WPF .NET Edition:
Active Query Builder ASP.NET Edition:
Active Query Builder Java Edition:
Active Query Builder ActiveX Edition:
Active Query Builder VCL Edition:
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!