Active Query Builder 3 Core Edition v.3.6.12.1169
- Snowflake SQL: Parsing of VARCHAR without char count has been fixed.
Active Query Builder 3 Core Edition v.3.6.11.1168
= The new method to append metadata from XML is added: MetadataContainer.AddFromXML(filename or stream). - Snowflake syntax: "LANGUAGE" is removed from the list of keywords. - SAP Hana: Minor SQL generation fixes are made. - MySQL: Minor fixes for queries with the "~" character.
Active Query Builder 3 Core Edition v.3.6.10.1167
= ODBCMetadataProvider: new properties are added to turn off some specific driver features that sometimes can improve the performance: IgnoreSchemaOnlyFlag and SkipLoadFieldsFromGetSchema. - MySQL: Logical conditions aren't suffixed with "=True" or "=False" anymore. - IBM DB2: System views are checked for existence before querying them.
Active Query Builder 3 Core Edition v.3.6.9.1166
+ Support for Snowflake DB SQL syntax has been added. - Assemblies are removed correctly now after uninstalling the product.
Active Query Builder 3 Core Edition v.3.6.6.1164
= QuickBooks: Support for square-brackets quoted identifiers has been added.
Active Query Builder 3 Core Edition v.3.6.5.1163
= QuickBooks (QODBC): Support for TOP clause is added, support for derived tables is turned off. = PostgreSQL: Backslash quotation for generic string literals has been removed. = Metadata serialization to XML: The "Loaded" flag for all types of objects is now set on for a namespace if child database objects of any type exist.
Active Query Builder 3 Core Edition v.3.6.3.1162
+ Initial support for QuickBooks (QODBC) SQL syntax has been added. + Performance and memory consumption improvements on loading large database schema has been made. ! "Loaded" flags for object types and referencing foreign keys are saved now in metadata XML files to avoid unnecessary SQL queries to be fired. = SAP HANA: Minor fixes are made: DISTINCT before TOP, PLACEHOLDER before alias, NVARCHAR builtin type.
Active Query Builder 3 Core Edition v.3.6.2.1161
+ The new event MetadataContainer.MetadataLoadingError is added to take additional actions on error executing queries to retrieve database schema. + The new event MetadataContainer.MetadataLoadingErrorNotification event is added to display notifications about errors executing metadata retrieval queries. One can suppress displaying error notifications to users by handling the MetadataLoadingError event and setting its Abort parameter to True to suppress firing of the MetadataLoadingErrorNotification event. + Logging of the metadata retrieval queries is fixed and improved. - Localization of messages in .NET Core assemblies has been fixed.
Active Query Builder 3 Core Edition v.3.6.1.1160
+ The Metadata Container Editor executable is included in the Professional and Trial installation packages. + Syntax providers: The new property QueryToLoadFieldsTemplate allows for customizing the query to load the list of fields for an object. + Metadata providers: The new property CommandTimeout allows for changing the timeout for metadata loading queries. = Oracle: Objects of excluded types (tables, views, procedures, synonyms) aren't loaded to the MetadataContainer anymore. - Oracle: Synonyms for objects that are not loaded to the metadata container aren't hidden now to speed-up a load of synonyms. = Consolidated Metadata Container demo: The "Show DataSources stats" button is added.
Active Query Builder 3 Core Edition v.3.6.0.1159
- Minor bugfixes and improvements have been 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!