Active Query Builder History v.2.1.4.546
SQL Text Editor changes: + Tab and Shift-Tab hot keys now shift the selected text block left and right. - Auto-capitalization of multi-word clauses that were added from suggestion list is fixed. = The "GROUP BY" and "ORDER BY" clauses are added to the suggestion list as templates so they might be entered in one click. - Mouse and keyboard selection behavior is fixed. - Incorrect suggestion window placement when the text is scrolled right or the caret is near to the right bound of the screen is fixed. - Text selection was disappearing on undo/redo operations. Fixed now. - Painting of sequence of Tab characters in selected state is fixed. Other changes: - Oracle: Support for method call expressions is made. - Alternate field names parsing is fixed. - Configuration Wizard: Fixed database connectivity issues. - Form Designer Converter: Fixed incorrect conversion of VB logical operators.
Active Query Builder History v.0.7.2
- Minor fixes for IE7,8 are made. - Minor improvements in touch functionality are made.
Active Query Builder History v.1.17.11.404
- Teradata: Numerous fixes and improvements are made.
Active Query Builder History v.0.7.1
+ Support for touch devices (iOS, Android, etc) is implemented.
Active Query Builder History v.1.17.11.403
= DevExpress references are updated to v.12.2.5.0. = Conditions like "a > 1 and a < 3" now loaded into the same criteria cell. = SQL Text Editor: "GROUP BY" and "ORDER BY" clauses are added to the suggestion list as templates so they might be entered at one click. - SQL Text Editor: Auto-capitalization of multi-word clauses that were added from suggestion list is fixed. - SQL Text Editor: The problem with transfer of input focus when using the Tab key to move out of the editor is fixed. - SQL Text Editor: The Find dialog was not disposed with the parent component. Fixed now. - SQL Text Editor: Reaction on selected text clicking is changed.
Active Query Builder History v.1.5.7.1124
- QueryBuilder was unable to load foreign keys from database connection if used with SQL92SyntaxProvider or SQL2003SyntaxProvider. Fixed now.
Active Query Builder History v.1.19.8
+ The x64 version is made. = The "CTE" prefix is added to the CTE sub-query tabs to distinguish them from other sub-queries. = Unnecesary parens are not written for nested conditions now.
Active Query Builder History v.1.19.8
= The "CTE" prefix is added to the CTE sub-query tabs to distinguish them from other sub-queries. = Unnecesary parens are not written for nested conditions now.
Active Query Builder History v.2.1.3.545
- DB2 Metadata Provider: Metadata objects loading is fixed. - MySQL Metadata Provider: Metadata objects loading is fixed. = Conditions like "a > 1 and a < 3" now loaded into one criteria cell.
Active Query Builder History v.2.1.3.544
+ The new CommandTimeout property is added to all metadata providers. = All source code demo projects are modified to use the Validating textbox event instead of the Leave event because Leave may sometimes occur twice and interefere with the going-on query update. This is new recommended practice. - Expression Editor: The problem with transfer of input focus when using the Tab key to move out of editor is fixed. - The bug in SubQuery.SQL and UnionSubQuery.SQL property setters is fixed. - Minor form designer code-generation issues are resolved. - The bug in alternate filed names parsing is fixed.
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!