Downloads

Active Query Builder History History

May 01, 2019

Active Query Builder History v.3.4.4

+ The new demo project to illustrate the component's usage in a Web API
  project with IoC controller, token-based state saving, and Angular client  
  has been added.
- Unintended datasource collapsing in derived tables on subquery switching 
  has been fixed.
- Minor bugs in demo projects have been fixed.
- Restoring layout for queries with virtual objects has been fixed.

April 30, 2019

Active Query Builder History v.3.5.15.1127

= SAP Hana: Support for (REPLACE/SUBSTR/OCCURRENCES)_REGEXPR, LEFT and RIGHT 
  functions has been added. 
- PostgreSQL: "table.*" is accepted as an ordinary ROW expression term.

April 30, 2019

Active Query Builder History v.3.5.15.1127

+ Visual Studio 2017/2019: WinForms and WPF controls are automatically 
  registered now in the Toolbox.
= Query Columns List: "= false" and "= true" are suggested now in condition 
  columns for logical expressions like EXISTS subqueries.
= Query Columns List: It is possible now to drag the last empty row to 
  arbitrary position to form a new query column there.
+ Query Columns List: Removal and reorder of selected rows is possible now 
  using the appropriate context menu commands.
+ Query Columns List: It is possible now to insert a new row above or below 
  the current row using the "Insert after/berfore" context menu commands.
- Query Columns List: multiple fixes and improvements in the process of 
  reordering rows by drag'n'drop.
- SQL Text Editor: Position of the context menu when the control wasn't 
  on the primary screen has been fixed.
- The incorrect increase of datasource top positions after switching between 
  subqueries has been fixed.
- LayoutSQL: Restoring layout for queries with virtual objects has been fixed.
- PostgreSQL: "table.*" is accepted as an ordinary SELECT item expression term.
= SAP Hana: Support for (REPLACE/SUBSTR/OCCURRENCES)_REGEXPR, LEFT and RIGHT
  functions has been added.

April 30, 2019

Active Query Builder History v.3.5.15.1127

+ Visual Studio 2017/2019: WinForms and WPF controls are automatically 
  registered now in the Toolbox.
= Query Columns List: "= false" and "= true" are suggested now in condition 
  columns for logical expressions like EXISTS subqueries.
= Query Columns List: It is possible now to drag the last empty row to 
  arbitrary position to form a new query column there.
+ Query Columns List: Removal and reorder of selected rows is possible now 
  using the appropriate context menu commands.
+ Query Columns List: It is possible now to insert a new row above or below 
  the current row using the "Insert after/berfore" context menu commands.
- Query Columns List: multiple fixes and improvements in the process of 
  reordering rows by drag'n'drop.
- LayoutSQL: Restoring layout for queries with virtual objects has been fixed.
- PostgreSQL: "table.*" is accepted as an ordinary SELECT item expression term.
= SAP Hana: Support for (REPLACE/SUBSTR/OCCURRENCES)_REGEXPR, LEFT and RIGHT
  functions has been added.

April 12, 2019

Active Query Builder History v.3.5.14.1126

= SQL formatting fixes and improvements have been made.
- Pervasive: The bug with parsing of some built-in functions has been fixed.
= MS SQL Server: The UseObjectNamesAsDefaultAliases attribute is turned on.
  This has allowed for less-qualified fields names generation.
= SQLQuery: The AddForeignKeyLinksForObject and AddLinkedObjectsFor methods
  are made public. The first method joins the specified datasource to existing
  objects in subquery if foreign key relationships exist between them.
  It returns the number of created joins. The second method adds intermediary
  objects to the subquery to get the specified datasource joined with the
  others and joins them appropriately.

April 12, 2019

Active Query Builder History v.3.5.14.1126

+ Query Columns List: A drop-down button is displayed now in Criteria column
  cells to suggest allowed logical operators to start building a condition.
= Query Columns List: The drop-down list for empty or fully selected Expression
  cells is now filled with fields from tables in the current sub-query, grouped
  by tables.
+ Query Columns List: When object or namespace is selected from the suggestion
  list in Expression cell *by mouse*, a dot is added automatically, so another
  suggestion is shown right after that for easier field selection of fields by 
  mouse.
= Query Columns List: Multiple rows selection by mouse and reordering of rows
  by drag'n'drop made easier now.
= Design Pane: Double click on a named query datasource header now switches
  the Design Pane to this named query.
= Subquery Navigation Bar: Minor usability fixes in managing subqueries joined
  with set operators (unions) are made.
= SQL formatting fixes and improvements have been made.
- The bug with incorrect saving of collapsed objects via the LayoutSQL
  property has been fixed.
- Pervasive: The bug with parsing of some built-in functions has been fixed.
= MS SQL Server: The UseObjectNamesAsDefaultAliases attribute is turned on.
  This has allowed for less-qualified fields names generation.
+ SQL Text Editor: The new SqlTextEditor.FillCustomSuggestions event has been
  added to add own suggestions before the list gets populated in a usual way.
= The SqlTextEditor.ActiveUnionSubQuery property is renamed to
  ExpessionContext.
= SQLQuery: The AddForeignKeyLinksForObject and AddLinkedObjectsFor methods
  are made public. The first method joins the specified datasource to existing
  objects in subquery if foreign key relationships exist between them.
  It returns the number of created joins. The second method adds intermediary
  objects to the subquery to get the specified datasource joined with the
  others and joins them appropriately.
- The bug with scrolling the PropertiesBar control has been fixed.
- The bug with drawing links for foreign key-based joins if alternate names 
  are used has been fixed.

April 12, 2019

Active Query Builder History v.3.5.14.1126

+ Metadata Editor is now available in the WPF Edition.
+ Query Columns List: A drop-down button is displayed now in Criteria column
  cells to suggest allowed logical operators to start building a condition.
= Query Columns List: The drop-down list for empty or fully selected Expression
  cells is now filled with fields from tables in the current sub-query, grouped
  by tables.
+ Query Columns List: When object or namespace is selected from the suggestion
  list in Expression cell *by mouse*, a dot is added automatically, so another
  suggestion is shown right after that for easier field selection of fields by 
  mouse.
= Query Columns List: Multiple rows selection by mouse and reordering of rows
  by drag'n'drop made easier now.
= Design Pane: Double click on a named query datasource header now switches
  the Design Pane to this named query.
= Subquery Navigation Bar: Minor usability fixes in managing subqueries joined
  with set operators (unions) are made.
= SQL formatting fixes and improvements have been made.
- The bug with incorrect saving of collapsed objects via the LayoutSQL
  property has been fixed.
- Pervasive: The bug with parsing of some built-in functions has been fixed.
= MS SQL Server: The UseObjectNamesAsDefaultAliases attribute is turned on.
  This has allowed for less-qualified fields names generation.
+ SQL Text Editor: The new SqlTextEditor.FillCustomSuggestions event has been
  added to add own suggestions before the list gets populated in a usual way.
= SQLQuery: The AddForeignKeyLinksForObject and AddLinkedObjectsFor methods
  are made public. The first method joins the specified datasource to existing
  objects in subquery if foreign key relationships exist between them.
  It returns the number of created joins. The second method adds intermediary
  objects to the subquery to get the specified datasource joined with the
  others and joins them appropriately.
- The bug with drawing links for foreign key-based joins if alternate names 
  are used has been fixed.

April 12, 2019

Active Query Builder History v.3.4.3

! Breaking change for ASP.NET Core: IActiveQueryBuilderService has been split into
  two services: IQueryBuilderService and IQueryTransformerService. Both services 
  are initialized with the services.AddActiveQueryBuilder method. The second service
  is needed if you use the CriteriaBuilder control which is tied to QueryTransformer
  object on the server side. Please refer to the Query Results demo project to
  review the usage code sample. 
+ All appropriate demo projects are ported to the ASP.NET Core platform. 
  (only for C# language). 
- Several demo projects for WebForms and MVC have been fixed. 
- Minor bug fixes are made.

March 13, 2019

Active Query Builder History v.3.4.2

- Expanding fields for tables in the search results of Database Schema Tree 
  by clicking on the expand/collapse indicator is possible now. 
+ The new AQB.Web.QueryBuilder.makeLayout method has been added to create 
  the component's layout. It should be used when the component is not visible
  on page load.

March 12, 2019

Active Query Builder History v.3.5.13.1125

- The Unicode "no-break space" symbol is added to the list of ignored chars. 
- The indication of command shortcuts in context menus has been corrected. 
- Unhandled exception on app closing if the focus is in the Query Column List has 
  been eliminated. 
- The bug with the layout restoration on some queries has been fixed.

Product Summary

 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:

News

Tweets

Testimonials

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!


Social networks