Bug Fixes in Stonefield Query SDK Version 3.2

As I mentioned in the previous blog entry, work has just begun on Stonefield Query version 3.2 and we've already fixed a bunch of issues. In no particular order:

• A problem that caused advanced layout reports to have too long of a page length when previewed or printed from the Preview window, resulting in some records not being displayed, was fixed.
  
• Under some conditions (sorting on a certain field data type when at least one record has a null value in that field), a single character was displayed rather than the entire contents of a field. This has been corrected.
  
• Charts now display correctly when there's missing data in some categories for some series.
  
• The Selected Field list in Step 2 of the report wizards now shows real table and field names correctly when you edit an existing report with the Display real table and field names option turned on.
  
• Renaming a report in the Reports Explorer didn't change the report header like renaming it in a report wizard; this was fixed. Also, copying a report now also changes the report header.
  
• The bookmarks panel in the Preview window is now sized correctly when clicking a field that runs a linked report and that report has bookmarks.
  
• A problem with not saving the email settings in the Options dialog was fixed.
  
• Specifying a period for the "CommonFiles" entry in Data.INI now means Stonefield Query's data files are located in the same folder as Data.INI rather than SFQuery.INI. Other types of relative paths are now handled correctly as well. Also, the program does a better job of handling Data.INI and its data files in "legacy" locations (locations other than the Data subdirectory of the application folder), and handles the case where its resource file (SQResource.DBF) exists in both the application folder and the Data subdirectory.
  
• Stonefield Query no longer exits with an error code when a report that has no records is run from another application; formerly, this prevented a report from running if multiple reports were specified.
  
• A problem with entering too long of a contact name in the Registration dialog was fixed.
  
• A problem with selecting the wrong database when reporting on more than one database at a time under some conditions was corrected. Also, an issue with similarly named data sources (for example, "Company" and "Company Database") was fixed.
  
• The cause of a rare "invalid index key" error when running a cross-tabulation report was fixed.
  
• An error caused by sorting on a field that exists on a report but doesn't appear when Summary Report is turned on was fixed.
  
• The numeric part of image file names created when a report is output to an image now have zeros for place holders (for example, Report0009.GIF and Report0010.GIF rather than Report9.GIF and Report10.GIF) so they appear in the correct sorted order in Windows Explorer.
  
• A bug that prevented sorting on a grouped field if you created a variable in the Advanced Report Designer on that field was fixed.
  
• HTML, Word, text, and table output now work correctly for chart reports. You can no longer output charts to RTF because the results aren't very good.
  
• Clicking the Values button in Step 2 of the report wizards nows displays an empty list of values rather than no list at all if the selected table contains no records.
  
• The Filter Condition dialog now shows the correct list of tables and fields in the Cross-Tabulation and Chart Wizards for new reports.
  
• Linking to another report on "display field from related table" fields now works correctly.
  
• Stonefield Query now properly handles a table or field that has "SELECT" at the end of its name (for example, "TaxSelect").
  
• Failure to connect to the update Web site when checking if a new version is available no longer causes an error message to be displayed.
  
• A second error that occurred while displaying the error message for a first error that may have occurred in the Preview window (for example, when running a linked report that had a problem) was resolved.
  
• The report dropdown list that appears on the Link page of the Field Properties dialog now shows the correct icon for chart reports.
  
• In previous versions, if you created a report but didn't go to Step 6 of the report wizard, everyone could run the report but only you could edit it. Now, the default is that everyone can both run and edit the report. You can, of course, change this in Step 6.
  
• A problem with the Chart Wizard hanging up after previewing a chart report that had no data in it was fixed.
  
• There is no longer a problem with displaying reports created by users with user names longer than eight characters.
  
• Pressing the Esc key while a report is running from one of the report wizards no longer causes an error.
  
• A problem with a filter condition containing an apostrophe under certain conditions was fixed.
  
• The Import Reports function now displays a proper error message if you select an empty file to import from.
  
• Clicking in one of the activation code boxes in the Registration dialog or Add License dialog after activating the program online added spaces to the activation code, making it invalid. This has been fixed.
  
• Changing the parameter information for a linked report caused the wrong information to be stored. This was corrected.
  
• An issue with the automatic update mechanism on Windows Vista systems was corrected.
  
• The Page Up and Page Down keys no longer move you from one page to another in a wizard; this feature prevented these keys from being used in other controls, such as dropdown lists. Instead, use Shift + Page Up and Shift + Page Down.
  
• An issue with the Login dialog sometimes appearing behind Stonefield Query (and thus not visible, leading you to think the program had hung up) was fixed.
  
• Email addresses selected in the Select Email Addresses dialog are now separated with commas rather than semi-colons to prevent an issue with some email programs.
  
• The New Folder function in the File menu is disabled for runtime licenses, since it doesn't make sense to create a folder if you can't create any reports in that folder.
  
• A problem caused by zooming the code window for a script, then clicking on a different item in the Configuration Utility, then saving the changes in the code window was corrected.
  
• Delimited field and table names for MySQL databases, which use the reverse apostrophe as the delimiter character, are now handled properly in Stonefield Query.
  
• Reports using an expression filter condition (such as "Order Date equals DATE() - 7") on tables that have a Select script are now handled properly.
  
• Calculated fields using non-Stonefield Query expressions that reference a field in another tables are now handled properly.
  
• The Configuration Utility now creates a help file correctly when the Target Application's Name setting is filled in but Need Target Application Directory is set to False.
  
• A bug that caused the wrong Default Language or Default Data Group for New Reports to be displayed in the Configuration Utility was fixed.
  
• A problem that caused a bogus error message when refreshing a data dictionary which doesn't contain all the tables in the database was corrected.
  
• An error that occurred when converting a data dictionary table named something other than REPMETA.DBF to the latest structure was fixed.
  
• Calculated fields using non-Stonefield Query expressions and calling functions native to the database engine (for example, "DATEADD(minute, 360, Order.OrderDate)") that return data types different than specified in the data dictionary now work properly in reports.
  
• A problem importing a data dictionary that didn't specify relationships was fixed.
  
• An issue that caused an error when you specified a value for Custom Properties for a field was fixed.
  
• The user no longers gets an ask-at-runtime dialog twice if a report has an ask-at-runtime filter condition and you have a DataEngine.FinalizeSQLStatement script.
  
• The user no longer gets a "no records matched" message if you display a dialog in the DataEngine.FinalizeSQLStatement script (such as calling the DataEngine object's GetValuesForField or GetValuesForParameter methods) and the user chooses Cancel in that dialog.
  
• The Configuration Utility now treats "PLAN" as a reserved word, so delimiters are automatically added around a table or field with that name.
  
• The ProjectLoaded property of the SQProxy object is now only set to True once the project has finished loading. In previous versions, it may have been set to True a little too soon, especially if you had a lot of scripts that slowed down startup.
  
• Fields using "R" for the Format property no longer have the Picture property applied twice when a value selected in the Values dialog is inserted into the Filter Condition dialog.
  
• An issue with MySQL when using multiple databases that caused the connection to the second database to fail because the user name and password were specified twice in the connection string was fixed.

Contact us if you've run into one of these issues and would like an interim build to resolve the problem (this is only available for current subscribers). Keep in mind that interim builds haven't been fully tested and the documentation hasn't been updated, so you shouldn't distribute this to customers unless necessary.