Knowledgebase
Stonefield Query Home > Stonefield Help Desk > Knowledgebase

Search help:


The "does not contain" operator is not returning all matching records in Stonefield Query for ACT!.

Solution

Applies to:

  • Stonefield Query for ACT!

Problem: The "does not contain" operator is not returning all matching records in Stonefield Query for ACT!.

Explanation: Stonefield Query for ACT! uses a component of the ACT! program called the ACT! Data Provider to access ACT! databases. This provider does not handle filters of this type correctly. Specifically, blank or empty values are not included in the results, when they should be.

Example: In the ACT! 2010 sample database, there are 200 contact records. A simple Stonefield Query report with a filter of Address 2 contains "s" correctly displays 61 contact records. However, a report with a filter of Address 2 does not contain "s" incorrectly displays only 23 contact records. There are 116 records with no value in the Address 2 field; these records should be included in the does not contain report, but they are not.

Solution: Add a filter condition using the is blank operator and an or connection. For the example above, the final filter would be:

Address 2 does not contain "s" or Address 2 is blank 

 
Was this article helpful? yes / no
Related articles "File is too large" error when running a report
Improving the Performance of Calculated Fields and Formulas
A message reading Microsoft OLE DB Provider for SQL Server : The multi-part identifier -name- could not be bound appears when running a report.
A message reading "Property CursorSchema has invalid value." appears when running a Stonefield Query for ACT! report.
A message reading "ACT! OleDB Provider for Reporting 2.0 : Invalid object name '#COMPANY_CONTACT'." appears when running a report.
Article details
Article ID: 13
Category: Frequently Asked Questions
Rating (Votes): Article rated 3.1/5.0 (41)

 
« Go back