Active Query Builder History v.3.5.6.1113
+ MS SQL Server: Support for SQL 2017 specific syntax of CONCAT_WS, TRANSLATE, and TRIM functions and query hints has been added.
Active Query Builder History v.3.5.6.1113
= Main localizations have been updated. + MS SQL Server: Support for SQL 2017 specific syntax of CONCAT_WS, TRANSLATE, and TRIM functions and query hints has been added. - Stored procedure parameter values validation in the Properties bar has been fixed. - The bug with disposing of custom Query Column List Control cells has been fixed.
Active Query Builder History v.3.5.6.1113
= Main localizations have been updated. + MS SQL Server: Support for SQL 2017 specific syntax of CONCAT_WS, TRANSLATE, and TRIM functions and query hints has been added. - Stored procedure parameter values validation in the Properties bar has been fixed. - The unhandled exception on clicking Condition cells has been eliminated.
Active Query Builder History v.3.5.6.1112
= References to DevExpress assemblies are updated to version 18.2. = MS SQL Server: Column aliases for functions are allowed now. - The Add Object dialog has been fixed. - The problem with join expressions in the WHERE clause in correlated subqueries has been fixed. - SQL Text Editor: Caret positioning by mouse has been made more accurate. - The notification about errors in Criteria expressions has been fixed.
Active Query Builder History v.3.5.6.1112
= MS SQL Server: Column aliases for functions are allowed now. - Expression Editor: Dragging functions from the list to the text editor has been fixed. - The problem with join expressions in the WHERE clause in correlated subqueries has been fixed. - SQL Text Editor: Caret positioning by mouse has been made more accurate. - The notification about errors in Criteria expressions has been fixed. - Other minor bug fixes have been made.
Active Query Builder History v.3.5.6.1112
= MS SQL Server: Column aliases for functions are allowed now. - The problem with join expressions in the WHERE clause in correlated subqueries has been fixed.
Active Query Builder History v.3.3.5
- The "OutputStream error" in WebForms with AJAX requests has been fixed. - The bug in the AddStoredProcedure function has been fixed. - The bug in the JavaScript header.setColumnWidth function has been fixed.
Active Query Builder History v.1.28.11
+ NexusDB syntax provider has been added. + MySQL: Support for Common Table Expressions for MySql v8+ has been added. + The new properties have been added to the QueryBuilder object to hide the controls for managing subqueries: SubQueryTabsVisible, UnionNavBarVisible. = Oracle: Support for ranking functions has been updated. - PostgreSQL: Parsing of the "AT TIME ZONE" clause and "EXTRACT(epoch FROM ...)" function has been fixed. - MS Access: Parsing of the TRUE and FALSE constants has been fixed. - The Union Navigation Bar scaling issues have been eliminated.
Active Query Builder History v.1.28.11
+ MySQL: Support for Common Table Expressions for MySql v8+ has been added. = Oracle: Support for ranking functions has been updated. - PostgreSQL: Parsing of the "AT TIME ZONE" clause and "EXTRACT(epoch FROM ...)" function has been fixed. - MS Access: Parsing of the TRUE and FALSE constants has been fixed. - The Union Navigation Bar scaling issues have been eliminated.
Active Query Builder History v.3.5.5.1111
- Memory leaks for undisposed AstNode objects have been eliminated. Took place when you have a long-life SQLContext object and use it to process multiple SQLQuery objects.
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!