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.

• You may need to tweak the settings in the Borland Database Engine (BDE). To do that, choose Settings from your Windows Start button, then choose Control Panel. Double-click on the BDE Administrator icon. Select the Configuration page in the BDE Administrator, click on the plus sign in front of Drivers to expand it, click on the plus sign in front of ODBC to expand it, and then click on the appropriate driver (SQL Server in the case of GoldMine Sales and Marketing or Microsoft dBase Driver in the case of GoldMine Business Contact Manager). If the SQLQRYMODE setting is Local, change it to Server (leave it alone if it's blank). Also, try adjusting the SCHEMA CACHE SIZE setting; some customers have reported that 64 works well. Finally, under the Object menu, choose Apply to save these changes. You can then exit the BDE Administrator. You may have to restart your system to have these settings take effect.

• If the performance problem mainly seems to be right after you start Stonefield Query, it's likely that the problem occurs while reading the GoldMine data structures so Stonefield Query knows about custom fields and detail types. Unfortunately, there isn't much you can do about that.
  

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.

When I report on the Combined Pending and History table and filter on Contact, I'm only getting records from Pending.

Because of the way contact names are stored in GoldMine, you need to use "contains" rather than "equals" for filters on this field.