Check to ensure that your default Windows printer supports landscape printing. If not, select another printer. This can especially be a problem in a Windows Terminal Server or Citrix environment.

Stonefield Query seems quite slow when I run a report.

This can be caused by a lot of things, some of which you likely can't control (such as a busy network, a slow network, etc.) and others you can. Here are some things to try:

• If you use Norton Anti-Virus 2001, ensure that Enable SmartScan Technology is turned off (with other versions of Norton Anti-Virus or other anti-virus programs, a different but similar setting is involved).

• Use a filter that returns a smaller set of records.

• Stonefield Query by default auto-fits each field so it's only as wide as the widest amount of data for that field. It does that by looking at each record to determine what the widest value is for every field. For large result sets, that can take some time (for example, 30 seconds for 200,000 records with 10 fields in one test we did). Turn off the Auto-fit column option in the Properties dialog for each field and manually enter a reasonable column width.
  

I'm using Stonefield Query in a Citrix or Windows Terminal Server environment. My session hung and after restarting it, I get an error indicating that I'm already logged into Stonefield Query when I try to get back in.

Logins are maintained in a file called LOGINS.DBF in the Stonefield Query data directory. If your Citrix or Windows Terminal Server connection wasn't properly closed, it's possible your login record was damaged. Fortunately, this is easy to fix: have anyone else who's running Stonefield Query exit the application, then delete LOGINS.DBF. This file is automatically recreated the next time you run Stonefield Query.

The help file doesn't display properly. When I select a topic in the Contents pane, the Topic pane shows "Action canceled" or some other warning message.

This is due to a Microsoft security update which was released in 2005. This update prevents the display of the help topics when the help file is not stored on your local machine or was downloaded from the Internet.

The solution is to edit the Windows registry to remove the security restriction Microsoft added with this update as described at http://support.microsoft.com/default.aspx?scid=kb;en-us;896358. Alternatively, you can copy the help file (SFQuery.CHM) to your local machine and specify the new location of the file in Data.INI. In that case, you may have to right-click SFQuery.CHM file in Windows Explorer, choose Properties, and click the Unblock button if it appears.

Stonefield Query for Sage Timberline Office appears to hang at "Checking Data Structures", but if left for 3-20 minutes, will actually start up.

Stonefield Query for Sage Timberline Office asks Timberline for a list of databases That are available for Querying. Unfortunately, Timberline does not store the exact locations of these databases, but rather relative paths. Additionally, it stores a list of potential drive locations in a seperate place. Stonefield Query must then check each of these to see if it is a valid database.

When Stonefield Query takes a long time to perform the above procedure, it usually means there is something delaying the "check" that is being done for each database. The most likely explanation is that you are no longer connected to the network/domain controller properly, and thus cannot access a shared drive. Another possibility is that a shared/mapped drive has become unavailable. You can check this by using a windows explorer window to connect to each of the mapped/shared drives, to see which one is causing the delay. To solve the problem, either remove the mapped drive, or solve the delay problem with the help of your network administrator.