Active Query Builder History v.1.27.0
+ Support for RAD Studio 10.2 Tokyo has been made. + MySQL: Support of MATCH full-text search operator has been added. = DB2: The new ObeySchemaListFromDriver boolean property (true by default) has been added. It prescribes to get the list of available databases from the driver (OLE DB or ODBC). - Access violation on removing active CTE has been eliminated. - DB2: The bug with selecting table owner instead of table schema for schema name has been fixed.
Active Query Builder History v.3.3.6.1053
= ODBC Metadata Provider: Better detection of servers that don't support schemas has been made. = SQL 92 Syntax Provider allows empty schema names now.
Active Query Builder History v.3.3.6.1053
= ODBC Metadata Provider: Better detection of servers that don't support schemas has been made. = SQL 92 Syntax Provider allows empty schema names now.
Active Query Builder History v.3.3.6.1053
= ODBC Metadata Provider: Better detection of servers that don't support schemas has been made. = SQL 92 Syntax Provider allows empty schema names now.
Active Query Builder History v.3.3.6.1042
- Minor refactorings have been made.
Active Query Builder History v.3.3.6.1042
- Dependent options in the properties sidebar panel are correctly enabled now upon changing the main property. - The bug with incorrect caret position, when word wrapping is turned on, has been fixed.
Active Query Builder History v.3.3.6.1042
- The bug with the editing of custom columns in the Query Columns List control has been fixed. = The text of join SQL expression in the Link Properties dialog and sidebar panel is wrapped by words now. - Dependent options in the properties sidebar panel are correctly enabled now upon changing the main property. - The bug with incorrect caret position, when word wrapping is turned on, has been fixed.
Active Query Builder History v.3.3.5.1041
+ MySQL: Support of MATCH full-text search operator has been made. = IBM DB2: The new DB2SyntaxProvider.ObeySchemaListFromDriver property has been added to ensure the priority of the list of objects received from the metadata provider (True by default). - IBM DB2: The bug with selecting table schema instead of table owner for schema name has been fixed. - The reference to MySql.Data assembly in MySQL metadata provider has been updated to the version 6.9.9.
Active Query Builder History v.3.3.5.1041
- SQL Text Editor: The ValidateContextMenu event has been fixed. + MySQL: Support of MATCH full-text search operator has been made. = IBM DB2: The new DB2SyntaxProvider.ObeySchemaListFromDriver property has been added to ensure the priority of the list of objects received from the metadata provider (True by default). - IBM DB2: The bug with selecting table schema instead of table owner for schema name has been fixed. - The reference to MySql.Data assembly in MySQL metadata provider has been updated to the version 6.9.9.
Active Query Builder History v.3.3.5.1041
+ MySQL: Support of MATCH full text search operator has been made. = IBM DB2: The new DB2SyntaxProvider.ObeySchemaListFromDriver property has been added to ensure the priority of the list of objects received from the metadata provider (True by default). - IBM DB2: The bug with selecting table schema instead of table owner for schema name has been fixed. - The reference to MySql.Data assembly in MySQL metadata provider has been updated to the version 6.9.9. - Adorner layer in the QueryColumnListControl has been 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!