Active Query Builder History v.3.0.5.1010
= MS SQL Server: Parsing speed is improved. - Layout of controls in the Add Object Dialog is fixed. - In some cases in the Database Schema tree in flat mode items weren't cleared correctly. Fixed now.
Active Query Builder History v.3.0.5.1009
+ Oracle: Database links support is made. To make objects from database links visible in Database Schema Tree, turn the the QueryBuilder.MetadataLoadingOptions.LoadDafaultDatabaseOnly property to False. + Sybase: Metadata retrieval from SAP IQ is made. + Flat view for the Database Schema Tree control is made. The new property QueryBuilder.DatabaseSchemaTreeOptions.ViewMode is added. Set it to Flat to turn the control into new mode. Default value is Tree. - The DatasourceAdding event is fired in all cases of adding object to the query by end-user. - MS SQL Server: Fetching stored procedure parameters from system catalog is fixed. - DB2: Fetching description for synonyms is fixed. - Teradata: Fields are sorted by default by ColumnId. - The behaviour of the MetadataFilterItem.Exclude setter is corrected. - Hiding hints for fields in DataSource field lists is fixed.
Active Query Builder History v.3.0.5.1009
+ Oracle: Database links support is made. To make objects from database links visible in Database Schema Tree, turn the the QueryBuilder.MetadataLoadingOptions.LoadDafaultDatabaseOnly property to False. + Sybase: Metadata retrieval from SAP IQ is made. + Flat view for the Database Schema Tree control is made. The new property QueryBuilder.DatabaseSchemaTreeOptions.ViewMode is added. Set it to Flat to turn the control into new mode. Default value is Tree. - The DatasourceAdding event is fired in all cases of adding object to the query by end-user. - MS SQL Server: Fetching stored procedure parameters from system catalog is fixed. - DB2: Fetching description for synonyms is fixed. - Teradata: Fields are sorted by default by ColumnId. - The behaviour of the MetadataFilterItem.Exclude setter is corrected.
Active Query Builder History v.2.10.5.773
= Metadata retrieval from Sybase IQ works fine now. - Metadata Filter: correct behaviour on filterItem.Exclude set - Cross thread error in the Quick Search box of Database Schema View is fixed. - MS SQL Server: Fetching stored procedure parameters from system catalog is fixed. - DB2: Fetching description for synonyms is fixed. - Teradata: Fields are sorted by default by ColumnId.
Active Query Builder History v.3.0.4.1008
+ Chinese (Taiwan) translation is added. + The new Query Transformer demo is added. - Advantage DB: The "use object names as default alias" flag is turned on. - Trial: Random aliases are kept the same for result query generated by the Query Transformer. - Query Transformer: SQL wasn't updated on changing the column.Visible property. Fixed now. - The OracleSyntaxProvider.IsSupportSubQueryCTE is set correctly now. - The bug with reseting SortType to Ascending after setting the QueryColumnListItem.SetSortOrder property is fixed.
Active Query Builder History v.2.11.0
= Icons are updated. - Sybase: Compatibility with Sybase IQ is restored.
Active Query Builder History v.3.0.4.1008
+ Chinese (Taiwan) translation is added. = Database Schema Tree: Descriptions for synonyms are taken from referred objects if it's not defined for synonym itself. + The new Query Transformer demo is added. + New demos are added to WinForms version: Query UI Events Demo, Interface Customization Demo, Datasource Fields Linking by Drag'n'Drop Demo - SQL Text Editor: Word wrapping is fixed. - Advantage DB: The "use object names as default alias" flag is turned on. - Trial: Random aliases are kept the same for result query generated by the Query Transformer. - Database Schema Tree: Only field nodes are shown under the table nodes now. - Query Transformer: SQL wasn't updated on changing the column.Visible property. Fixed now. - Parsing of the "in (subquery)" expressions in condition cells is fixed. - The OracleSyntaxProvider.IsSupportSubQueryCTE is set correctly now. - The error on using Quick search in the Add Object Dialog is fixed. - The bug with reseting SortType to Ascending after setting the QueryColumnListItem.SetSortOrder property is fixed.
Active Query Builder History v.3.0.4.1008
+ Chinese (Taiwan) translation is added. = Database Schema Tree: Descriptions for synonyms are taken from referred objects if it's not defined for synonym itself. + The new Query Transformer demo is added. - Overlapping items bug in DataSource control is fixed. - Clicking on a non-focused check box in the Visible column of Query Columns List didn't affect the state. Fixed now. - SQL Text Editor: Word wrapping is fixed. - Advantage DB: The "use object names as default alias" flag is turned on. - Now the hints for fields in DataSource field lists are hidden after right clicking on a DataSource. - Trial: Random aliases are kept the same for result query generated by the Query Transformer. - Database Schema Tree: Only field nodes are shown under the table nodes now. - Query Transformer: SQL wasn't updated on changing the column.Visible property. Fixed now. - Drawing of arrows at the end of links in case of Left/right outer joins is fixed. - Parsing of the "in (subquery)" expressions in condition cells is fixed. - The OracleSyntaxProvider.IsSupportSubQueryCTE is set correctly now. - The bug with reseting SortType to Ascending after setting the QueryColumnListItem.SetSortOrder property is fixed.
Active Query Builder History v.2.10.17
+ The Sub-query Navigation Bar is re-designed. + New design and icons are applied. + Chinese (Taiwan) translation is added. + Select lists for month and year are added to the dropdown editor for date values in Criteria Builder. + The new "Clear" button is added to Criteria Builder. + The new event QB.Web.Application.GridComponent.CustomEditControl is added to override the default cell editor type. + The new ObjectTreeView.SortOrder property that determines ascending or descending order is added. - The bug with not keeping the original objects order when SortingType is set to "None" is fixed. = Database Schema Tree: Descriptions for synonyms are taken from referred objects if it's not defined for synonym itself. = Advantage DB: The "use object names as default alias" flag is turned on. - Trial: Random aliases are kept the same for result query generated by the Query Transformer. - Database Schema Tree: Only field nodes are shown under the table nodes now. - Query Transformer: SQL wasn't updated on changing the column.Visible property. Fixed now. - Parsing of the "in (subquery)" expressions in condition cells is fixed.
Active Query Builder History v.2.10.5.771
+ Chinese (Taiwan) translation is added. = Database Schema Tree: Descriptions for synonyms are taken from referred objects if it's not defined for synonym itself. = Advantage DB: The "use object names as default alias" flag is turned on. - Trial: Random aliases are kept the same for result query generated by the Query Transformer. - Database Schema Tree: Only field nodes are shown under the table nodes now. - Query Transformer: SQL wasn't updated on changing the column.Visible property. Fixed now. - Parsing of the "in (subquery)" expressions in condition cells is fixed. - The OracleSyntaxProvider.IsSupportSubQueryCTE is set correctly now. - The error on using Quick search in the Add Object Dialog is fixed. - The bug with reseting SortType to Ascending after setting the QueryColumnListItem.SetSortOrder property is 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!