Active Query Builder History v.2.9.1.694
+ The new MetadataStructureChanged event is added. It is fired on changing the value of MetadataStructure property. This happens automatically on turning the Database Schema Tree to display search results and back.
Active Query Builder History v.2.9.1.693
- Null Reference Exception that was raised with some databases using the "Type, Name (Except Fields)" sorting mode in the tree is eliminated. = Query Transformer and Criteria Builder: The new OutputColumn.DataType property is added to adjust the column datatype to change the editor type in Criteria Builder for this column.
Active Query Builder History v.2.6.2
- GUI fixes in Criteria Builder are made.
Active Query Builder History v.1.24.4
= SQL parser fix is made. (affects all SQL dialects)
Active Query Builder History v.1.24.4
= SQL parser fix is made (affects all SQL dialects).
Active Query Builder History v.2.9.1.692
- CriteriaBuilder: AutoSize and Anchor properties conflict is resolved. - DevExpress: List sorting in the AddObjectForm is fixed. + The new MetadataContainer.Clear() method is added.
Active Query Builder History v.2.6.1
- Minor GUI bugfixes are made.
Active Query Builder History v.1.24.3
+ SQLite: Backtick quoted identifiers are supported now. + SQLite: Support for Common Table Expressions is made. It was added in SQLite v3.8.3 released on 2014-02-03. + The new property SelectListOptions.CreateColumnAliasesForUnnamedColumns is added to instruct the component to add aliases for unnamed fields (expressions, aggregates) automatically. It is turned on by default. = MS SQL Server, DB2: QueryTransformer now uses ROW_NUMBER ranking function to implement Skip and Take methods for these servers. - Add Linked Objects menu now creates links for all fields for multi-column foreign keys (not only for the first field). - Error on deleting datasource in subquery is fixed. - MS SQL Server: Pound symbol is removed from the list of valid identifier letters.
Active Query Builder History v.1.24.3
+ Fonts scaling support is made. + SQLite: Backtick quoted identifiers are supported now. + SQLite: Support for Common Table Expressions is made. It was added in SQLite v3.8.3 released on 2014-02-03. + The new property SelectListOptions.CreateColumnAliasesForUnnamedColumns is added to instruct the component to add aliases for unnamed fields (expressions, aggregates) automatically. It is turned on by default. = MS SQL Server, DB2: QueryTransformer now uses ROW_NUMBER ranking function to implement Skip and Take methods for these servers. - Add Linked Objects menu now creates links for all fields for multi-column foreign keys (not only for the first field). - MS SQL Server: Pound symbol is removed from the list of valid identifier letters. - Error on canceling execution of non-SELECT statements is fixed. - Error on deleting datasource in subquery is fixed.
Active Query Builder History v.2.9.1.691
+ New overload is added for the ShowAddObjectForm() method with the MetadataStructure parameter allowing to customize metadata representation in the form. + The new QueryColumnListOptions.CreateColumnAliasesForUnnamedColumns property is added to instruct the component to add aliases for unnamed fields (expressions, aggregates) automatically. It's turned on by default. + SQLite: Support for Common Table Expressions (CTE) is made. - SQLite: Support for backtick-quoted identifiers is made. - Firebird: Support for the WEEK date part is added. - MySQL: Support for quoted characters in string literals is made.
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!