Active Query Builder History v.3.7.2.1175
+ The installer creates local NuGet source with Active Query Builder packages. - The bug with saving reusable queries has been fixed. - Minor bugs have been fixed.
Active Query Builder History v.3.7.2.1175
+ The installer creates local NuGet source with Active Query Builder packages.
Active Query Builder History v.3.7.1.1174
+ Support for .Net Core 2.2 and 3.1 support has been added. - Snowflake SQL: LIMIT is treated as a valid identifier now. - Metadata calculation for virtual objects has been fixed. - Snowflake SQL: "POSITION" is removed from the keywords list. - Snowflake SQL: The ambiguity in the parsing of complex comparison expressions has been fixed.
Active Query Builder History v.3.7.1.1174
+ Support for .Net Core 2.2 and 3.1 support has been added. - Snowflake SQL: LIMIT is treated as a valid identifier now. - Metadata calculation for virtual objects has been fixed. - Snowflake SQL: "POSITION" is removed from the keywords list. - Snowflake SQL: The ambiguity in the parsing of complex comparison expressions has been fixed.
Active Query Builder History v.3.7.1.1174
+ Support for .Net Core 2.2 and 3.1 support has been added. - Snowflake SQL: LIMIT is treated as a valid identifier now. - Metadata calculation for virtual objects has been fixed. - The drawing of the DockPanel caption in large-scaling modes has been corrected. - Snowflake SQL: "POSITION" is removed from the keywords list. - Snowflake SQL: The ambiguity in the parsing of complex comparison expressions has been fixed.
Active Query Builder History v.3.7.1.417
= Reference to the AQB Core assembly has been updated.
Active Query Builder History v.3.6.15.1172
= Metadata Editor: Minor error reporting fixes and improvements on loading data from XML files have been made. = Source code of the standard metadata providers (MS SQL Server, OLE DB, ODBC) has been added to all distributives. - Snowflake SQL: Keyword issues have been fixed. - PostgreSQL: Parsing of "TABLE.*" as a correct AST node at the top level of the SELECT clause has been fixed. - MySQL: Parsing of the "POSITION" clause has been fixed.
Active Query Builder History v.3.6.15.1172
= Metadata Editor: Minor error reporting fixes and improvements on loading data from XML files have been made. = Source code of the standard metadata providers (MS SQL Server, OLE DB, ODBC) has been added to all distributives. - Snowflake SQL: Keyword issues have been fixed. - PostgreSQL: Parsing of "TABLE.*" as a correct AST node at the top level of the SELECT clause has been fixed. - MySQL: Parsing of the "POSITION" clause has been fixed.
Active Query Builder History v.3.6.15.1172
= Metadata Editor: Minor error reporting fixes and improvements on loading data from XML files have been made. = Source code of the standard metadata providers (MS SQL Server, OLE DB, ODBC) has been added to all distributives. - Snowflake SQL: Keyword issues have been fixed. - PostgreSQL: Parsing of "TABLE.*" as a correct AST node at the top level of the SELECT clause has been fixed. - MySQL: Parsing of the "POSITION" clause has been fixed.
Active Query Builder History v.3.6.15.415
- Cardinality labels for links created by the user are displayed correctly now. = Reference to the AQB Core assembly has been updated.
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!