There are numerous new features in this release.
- A new chart type is now available: Donut, which is similar to Pie but with a hole in the middle.
- The default settings for a new chart give it a more modern appearance, such as flat rather than 3-D and better colors.
- You can now define a chart with a second values field; this field is charted as a second series against the right axis.
- The Output each group as a separate file and Output each group as a separate email options now support charts on quick reports. In that case, each file has its own chart related to the group the file is for.
- The Filter Condition dialog now uses a more modern date picker control.
- The Add timestamp to file name setting is now available even when Erase file after email sent setting is turned on in the Output page of the Reports Explorer.
- A new output type is now available: Microsoft Word (*.docx), which creates Word 2007 or later files. The former Microsoft Word (*.doc) output type was renamed to Microsoft Word 97-2003 (*.doc) so you can tell them apart. The docx format is preferred as it's more accurate.
- The Check for Updates function in the Help menu is now only available if you are logged into Stonefield Query as an administrator.
- You can now change settings in the Format page of the Field Properties dialog for numeric fields in columns of cross-tab reports.
- The prompts in the Email page of the Options dialog have been changed to reflect the fact that SMTP is the preferred setting since MAPI can be unreliable, especially when emailing a scheduled report.
- There's a new ReportEngine.BeforeCreateFile script that's called just before a report is output to a file or emailed. You can use this to change the report or output properties.
- You can now encrypt the file created when a report is output to file or email. In the case of a PDF file, the file itself is encrypted; other file types are added to an encrypted ZIP file which is used as the attachment instead of the file. To do that, create a ReportEngine.BeforeCreateFile script and set the new Report.EncryptPassword property to the desired password. If this property isn't blank, the file is encrypted.
- The Report object also has a new Folders property containing a comma-delimited list of the folders the report belongs to.
- The Application object now has a DashboardChart property containing the chart number being generated when a dashboard is previewed and 0 otherwise. This allows a script such as DataEngine.BeforeResultSetRetrieved to do different things for different charts such as prompting for values for the first one.
- The title bar of the window displayed when you choose the View Table Contents or View Field Contents functions now shows the number of records in the table.
- The Filter Data Dictionary dialog now uses a more modern date picker control.
- The Refresh function now removes fields from the data dictionary that were removed from their tables.
- Clicking the project location displayed in Studio's status bar now opens that location in Windows Explorer.
- The tooltip for the Join Type drop-down list in the properties pane for relationships now gives a better explanation of left and right outer joins.
- Creating a GetDataSources script for a database now turns off and disables the User Can Manage Data Sources configuration setting since those two are mutually exclusive.
- Clicking the Test button for a relationship now gives a warning if one of the tables is a virtual table since that can't be tested.
- You can now copy the serial number in Studio's About dialog, making it easier to specify your serial number when creating a support ticket.
- You can now use WSSetup.exe to do a workstation install from the server where the SDK is installed. This allows someone using Stonefield Query in-house to not have to create a setup installer to allow users to access the report designer.
- If you're querying against a Visual FoxPro database and you create a calculated field using the ALLTRIM() function as the expression, such as ALLTRIM(MyField), Stonefield Query may find more records than expected when the user filters on that calculated field due to the way string comparisons are done. In that case, add "UseAnsi=Y" to the [Options] section of SFQuery.INI. Note that isn't the same as the "UseAnsi=Y" setting in Data.INI; see the Stonefield Query help file (SFQuery.chm) for information on that setting.
- Reading the structure of a database now ignores the trace_xe_* tables added in Microsoft SQL Server 2012.
- MSMAPI32.OCX and MSCOMCT2.OCX are now longer installed or deployed to end-users because we now use different components for sending email via MAPI and date picker controls.