Using Stonefield Query on 64-bit Windows

Although it's a 32-bit application, Stonefield Query works just fine on 64-bit versions of Windows, including Windows Vista, Windows 7, Windows Server 2003, and Windows Server 2008.

One known issue with Windows, however, is that 32-bit applications can access 32-bit system DSNs, 32-bit user DSNs, and 64-bit user DSNs, but not 64-bit system DSNs. Since the default ODBC Administrator is the 64-bit version (you can run the 32-bit version from the SysWoW64 subdirectory of the Windows folder if necessary), any system DSNs you create aren't visible to Stonefield Query. So, either create user DSNs rather than system DSNs or use the 32-bit ODBC Administrator to create your DSNs.

This impacts any version of Stonefield Query that uses ODBC DSNs rather than connection strings, including:

• Stonefield Query SDK (if you turn on the User Can Manage Data Sources configuration setting)
• Stonefield Query for GoldMine
• Stonefield Query for HEAT
• Stonefield Query for MAS 90 and 200
• Stonefield Query for Sage Accpac ERP
• Stonefield Query for Sage BusinessVision
• Stonefield Query for Sage Pro ERP (SQL version)

Stonefield Query for Sage Accpac ERP Video Available

We've posted a video providing an overview of Stonefield Query for Sage Accpac ERP. It's about 16 minutes long and goes over the various features of Stonefield Query, including: how to create quick reports, labels, cross-tab reports, and charts; how to schedule reports; and how to output reports to various kinds of files, such as Microsoft Excel or PDF. It also discusses how easy Stonefield Query makes it to report on optional fields in Sage Accpac ERP, something that's very difficult to do using other reporting solutions.

We'll do one for Sage Pro ERP in the near future.

Stonefield Query Version 3.2 Build 3082

We posted updated versions of the Stonefield Query SDK, Stonefield Query for Sage Accpac ERP, and Stonefield Query for Sage Pro ERP today with the following changes.

All Versions

• You no longer get an error in the Registration dialog if you renamed the ADMIN user.
• The size of Avery 5266 labels was fixed so they now print properly (the sizing information provided to us by Avery was incorrect).
• You can no longer drag a report or folder to a blank portion of the reports list; previously, this caused the report or folder to disappear.
• The titles for the Dynamic Color and Dynamic Font Style dialogs are now localizable.
• The Dynamic Color and Dynamic Font Style dialogs and all dialogs in the Advanced Report Designer now use the same icon as the rest of the Stonefield Query dialogs.
• Certain types of fields that gave an error when used in a filter condition that compares another field to them no longer do so.
• Fields that use a drop down list of values in the ask-at-runtime Filter Condition dialog now display the same value as the last time when you run a report several times.
• Filtering on some types of calculated fields when those fields aren't included in the report no longer causes an error.
• Stonefield Query is no longer sensitive to the date format for dates passed as parameters to linked reports.
• Running a report that contains links no longer loses the list of databases the second time you run it. Also, the filter conditions in the FilterConditions object are now valid between runs of linked reports. Also, the header for the parent report is no longer changed to that of the child report.
• Issues previewing reports when Windows is set to Chinese (PRC) have been corrected.
• Turning off the Display Date Only option in the Field Properties dialog for a datetime field resulted in that field being displayed as MM/DD/YYYY rather than the correct Windows setting when used as a filter condition. This was corrected.

SDK

• Errors that occurred when generating help files when Windows is set to Chinese (PRC) no longer occur.
• The Generate Setup function now include the logo image file in the generated ISS script file.
• You can now specify a custom control class to appear in the Setup dialog using the Setup.Settings script.
• An error that occurred when you selected a data group or user group in the Configuration Utility when you have multiple data dictionaries and the second data dictionary contains the same tables as the first one but in different data groups was fixed.
• Setup scripts generated from the Configuration Utility now put the runtime files in the Stonefield Query program folder.
• Although this situation doesn't make sense, Stonefield Query no longer gives an error if you use the Display Field From Related Table option on a foreign key field and the field you choose to display is the primary key from the related table and these fields have the same name.

Sage Accpac ERP

• Application startup performance was improved.

Sage Pro ERP

• We've added support for Return Merchandise Authorization (RM) tables.
• The Detail Line Explanation field in the GL Posted Transaction Details File (GLDENT.GLTDES) now displays the actual description rather than XML.
• Some missing enumeration values were added, including "C" (for "Credit Card") to the PPRIORITY field in APMAST, APMST, and APYMST and "D" (for "Drop Shipment") to the SOTYPE field in SOYTRN and SOTRN.