Active Query Builder History v.2.6.0.615
+ Criteria Builder: If criteria column contains a foreign key, the control now shows referenced table in the lookup window. + Criteria Builder: The IsValid() method is added. It allows to check whether all values in the control are filled and valid. - Auto-detection of Teradata, MS SQL CE and Azure database servers is fixed. - Sybase ASE: A workaround for buggy AseDataReader.GetOrdinal() ADO provider method is made. - Oracle: Parsing of PARTITON with OUTER JOIN is fixed. - PostgreSQL: Support for AT TIME ZONE expression is made. - PostgreSQL: Support for the ROW constructor expression is made. - PostgreSQL: The EXTRACT function is fixed.
Active Query Builder History v.1.1.0
= Razor Query Results demo project is updated: Criteria Builder is added. = Minor API changes are made.
Active Query Builder History v.1.0.7
+ The new CriteriaBuilder control is made for visual composing of criteria. + Query Results demo project is updated: Criteria Builder is added. + Field lookup list in Expression column of the Query Results Grid is improved. Search by typing in inline cell edtor is made. Jump between search results with the Up and Down arrow keys. - The bug with not refreshing metadata on clicking the Reconnect button is fixed.
Active Query Builder History v.2.5.5.614
= MS SQL Server: Query builder now loads only accessible databases, for which the user has CONNECT provilege. - Switching of Syntax Provider without reloading the query is possible now. - Foreign keys where affected when metadata filtering is used. Fixed now.
Active Query Builder History v.1.22.5
+ PostgreSQL: The WINDOW clause is supported now. + PostgreSQL: The ORDER BY clause in aggregate functions is supported now. + PostgreSQL: The ROW constructor expressions are supported now. + PostgreSQL: The AT TIME ZONE is supported, the EXTRACT function is updated. = Linked Objects Menu: Linked object names are sorted alphabetically now. - Loading of WHERE joins with subqueries referencing other datasources is fixed.
Active Query Builder History v.1.22.5
+ PostgreSQL: The WINDOW clause is supported now. + PostgreSQL: The ORDER BY clause in aggregate functions is supported now. + PostgreSQL: The ROW constructor expressions are supported now. + PostgreSQL: The AT TIME ZONE is supported, the EXTRACT function is updated. = Linked Objects Menu: Linked object names are sorted alphabetically now. - Loading of WHERE joins with subqueries referencing other datasources is fixed. - Access Violation error when using miltiple Query Builders with ODBC connection string is fixed.
Active Query Builder History v.2.5.5.613
+ ODBC: Metadata loading for old ODBC drivers is fixed. - Unpaired fields in foreign key definitions (MetadataForeignKey) are ignored when adding links on the Design Area.
Active Query Builder History v.2.5.4.612
- The broken auto-layout of objects on sub-query tabs when loading a query from the text is fixed. - Tab order in Datasource Properties form is fixed. - SQL Text Editor: Backward search from the end of text is fixed.
Active Query Builder History v.2.5.4.611
- The NullReferenceException in the AutoSyntaxProvider is fixed. It was raised when the MetadataProvider property was set to null.
Active Query Builder History v.2.5.4.610
= DevExpress references are updated to v.13.1.8.0.
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!