Active Query Builder History v.1.5.5.92
+ The new HideSingleDatabaseNode property is added to the QueryBuilder.MetadataTreeOptions to hide unnecessary database node if all objects are loaded from the same database. + New properties are added to the Universal syntax provider: AutoDetectServer: Boolean; allow/deny database server autodetection. PreferredServer: TacUniversalSyntaxServerType; defines database server to start the autodetection routine from. UsedServer: TacUniversalSyntaxServerType; determines detected database server. - DB2 syntax: bug with some keywords that were used as identifiers is fixed.
Active Query Builder History v.1.9.0.7
+ The new demo is added to illustrate ability to replace real object and field names with user-friendly alternate names (Demos\AlternateNames). + MS SQL: The new way to load list of available databases is added. + Demo projects are updated to show new settings dialog for the Universal syntax provider. * New properties are added to the Universal syntax provider: AutoDetectServer: Boolean; allow/deny database server autodetection. PreferredServer: TacUniversalSyntaxServerType; defines database server to start the autodetection routine from. UsedServer: TacUniversalSyntaxServerType; determines detected database server.
Active Query Builder History v.1.9.0.7
+ MS SQL: The new way to load list of available databases is added.
Active Query Builder History v.1.5.4.91
+ Query properties dialog for PostgreSQL syntax is implemented. + Firebird syntax: common table expressions are supported now. - MS SQL: Fixed loading of database list under a restricted user role.
Active Query Builder History v.1.9.0.5
- Fixed critical bug caused the component to generate wrong SQL query criteria in some cases (introduced in 1.9.0.2).
Active Query Builder History v.1.9.0.5
- Fixed critical bug caused the component to generate wrong SQL query criteria in some cases (introduced in 1.9.0.2).
Active Query Builder History v.1.5.3.90
+ Tne new demo project is added to illustrate ability to modify queries programmatically (QueryModificationDemo). = Minor optimizations are made.
Active Query Builder History v.1.5.2.79
+ The new syntax provider UniversalSyntaxProvider is added. It is based on the ANSI SQL/92 syntax but allows to determine most of popular database servers, successfully retrieve metadata and apply specific settings for them to let the user build simple queries for these servers. Please note that this does not mean that the Universal Syntax Provider could be a suitable replacement for specific database syntax providers, as it strictly follows the rules of ANSI standard, that may lead to many incompatibilities while working with specific database servers. Working with the Standard version, use the Auto Syntax Provider in case of necessity to detect database server automatically. + The new full-featured MDI Demo application with source code is added to the Trial and Standard versions. - Drawing of visual join link arrows is fixed.
Active Query Builder History v.1.9.0.4
+ Tne new demo project is added to illustrate ability to modify queries programmatically (Demos\QueryModificationDemo). * Chinese, Italian, German and Portuguese (Brazil) localizations files are updated. Spanish, Czech, Turkish and Japanese localization require updating. Please let us know if you can update one of them. + Two new events are added to update object metadata information if necessary: OnObjectMetadataLoading(TacMetadataContainer, TacMetadataObject); OnObjectMetadataLoaded(TacMetadataContainer, TacMetadataObject); + The new QueryToLoadFields property is added to the TacMetadataObject interface. Read this property to get SQL statement that should be executed to read result columns from dataset and fill the fields definition list for this database object. + Now the Universal Syntax Provider is able to retrieve metadata from SQLite and Informix database servers. + TacUniversalSyntaxProvider: The new AutodetectConnectedServer(ASQLContext) method is added to re-detect connected server manually + Localizer: Ability to load localized strings through the event is implemented + MS SQL Syntax: Added support for the "OPENQUERY" clause. - MySQL: Small fix is made in the loading relations procedure. - Oracle: Small fix is made in loading objects procedure. - Add Object Window: Fixed bug that does not allowed to add views and procedures to the query.
Active Query Builder History v.1.9.0.4
* Chineese, Italian, German and Portuguese (Brazil) localizations files are updated. Spanish, Czech, Turkish and Japanese localization require updating. Please let us know if you can update one of them. + Two new events are added to update object metadata information if necessary: QueryBuilder.OnObjectMetadataLoading(IMetadataContainer, IMetadataObject) QueryBuilder.OnObjectMetadataLoaded(IMetadataContainer, IMetadataObject) + The new QueryToLoadFields property is added to the IMetadataObject interface. Read this property to get SQL statement that should be executed to read result columns from dataset and fill the fields definition list for this database object. + Now the Universal Syntax Provider is able to retrieve metadata from SQLite and Informix database servers. + MS SQL Syntax: Added support for the "OPENQUERY" clause. - MySQL: Small fix is made in the loading relations procedure. - Oracle: Small fix is made in loading objects procedure. - Add Object Window: Fixed bug that does not allowed to add views and procedures to the query.
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!