Below is the list of fixes and improvements in Active Query Builder ActiveX Edition v.188.8.131.52.
+ New feature: Virtual database objects and fields. It allows to hide complex expressions and sub-queries back of ordinary fields and save derived tables as ordinary database objects. + New properties are added to support virtual database objects and fields: IMetadataField.Expression and IMetadataObject.Expression (BSTR). IMetadataField.Expression can contain any correct SQL expression; IMetadataObject.Expression can contain any correct "datasource": an SQL expression which can be used in the FROM clause, i.e. object name, subquery (derived table), etc. The component will replace all mentions of such fields and objects in result SQL with this expression. Read the IActiveQueryBuilderX.SQLForServer property to get the expanded result SQL text. + The new property IActiveQueryBuilderX.LoadJoinsFromWhereClause: VARIANT_BOOL is added. Using this property you can instruct Query Builder to not treat expressions like "tbl1.FieldName = tbl2.FieldName" as joins. They will be loaded as generic WHERE clause expressions instead. - Metadata relations loading from Sybase ASE is fixed. - The IActiveQueryBuilderX.TreeOptions.TreeWidth and IActiveQueryBuilderX.TreeOptionsMetadata.TreeWidth properties are reflect changes in UI immediately now. - DB2: Metadata filtering is fixed. - Subquery tab doesn't disappear when user closes a derived table. Fixed now.
[ Legend: ] [ + New feature ] [ = Improved/changed feature ] [ - Bug fix ] [ ! Important notice ]
You can always get the latest trial version of Active Query Builder ActiveX Edition at the download page.
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!