Active Query Builder History v.0.7.20
+ Alias is automatically set now for a newly added column to avoid column name duplication. + The new QueryBuilderControl.UserMessage event is added to override the default way to show warnings. - Incorrect warning message on adding same named columns to the query is fixed. = Activation Wizard is updated.
Active Query Builder History v.0.7.19
= Database connection is closed now at the end of client HTTP request handling. - The new property QueryBuilderControl.PersistentConnection is added to instruct the component to keep database connection opened till the session expiration. - Touch interface is fixed.
Active Query Builder History v.1.18.3.420
= Internal change: Binding column names is not performed now if fieldless datasources are in the scope.
Active Query Builder History v.1.18.3.418
+ The new MetadataContainer.ConnectionIdle event is added. It allows for closing the database connection if it's not desirable to keep it open during the work session.
Active Query Builder History v.2.2.6.568
+ The new MetadataContainer.ConnectionIdle event is added. It allows for closing the database connection if it's not desirable to keep it open during the work session. - The SQLChanging property was kept on after the query parsing error. Fixed now.
Active Query Builder History v.1.18.2.417
+ SQL Text Editor and Expression Editor: The new properties are added to
improve usability of the code completion feature and to prioritize the
content of suggestion lists:
* The ShowSuggestionAfterCharCount property determines number of chars
that should be typed before the suggestion list will popup;
* The SuggestionListContent property allows to filter the content of
suggestion list (keywords, SQL functions and metadata objects);
* The KeepMetadataObjectsOnTopOfSuggestionList property being set to True
instructs to act exactly what is written.
= SQL Text Editor: Background processing is reworked to the Single Thread
Apartment (STA) model to eliminate problems with drag and drop registration
in parent application.
Active Query Builder History v.2.2.5.567
+ SQL Text Editor and Expression Editor: The new properties are added to
improve usability of the code completion feature and to prioritize the
content of suggestion lists:
* The ShowSuggestionAfterCharCount property determines number of chars
that should be typed before the suggestion list will popup;
* The SuggestionListContent property allows to filter the content of
suggestion list (keywords, SQL functions and metadata objects);
* The KeepMetadataObjectsOnTopOfSuggestionList property being set to True
instructs to act exactly what is written.
= SQL Text Editor: Background processing is reworked to the Single Thread
Apartment (STA) model to eliminate problems with drag and drop registration
in parent application.
Active Query Builder History v.0.7.18
- The importSQL JavaScript function works fine now with hidden SQL Editor.
Active Query Builder History v.1.18.1.415
- The problem with incorrect aliases in ORDER BY in some cases is fixed. - SQL Text Editor: The REGEXP_LIKE function is added to the suggestion list.
Active Query Builder History v.2.2.4.566
+ The new events are added to metadata providers: BeforeSqlExec and AfterSqlExec. They might be useful for tracing SQL queries sent to the database server. - The problem with incorrect aliases in ORDER BY in some cases is fixed. - SQL Text Editor: The REGEXP_LIKE function is added to the suggestion list.
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!