Knowledgebase
Stonefield Query Home > Stonefield Query Help Desk > Knowledgebase

Search help:


A message reading "ACT! OleDB Provider for Reporting 2.0 : Invalid object name '#COMPANY_CONTACT'." appears when running a report.

Solution

Applies to:

  • Stonefield Query for ACT!

Problem: A message reading "ACT! OleDB Provider for Reporting 2.0 : Invalid object name '#COMPANY_CONTACT'." appears when running a report. The report includes an exclusion filter.

Explanation: The ACT! OleDB Provider is a component of the ACT! program used by Stonefield Query to access ACT! database information. This error message is due to a bug in the provider where it is unable to process a complicated command from Query.

Solution: Normally, Stonefield Query creates a single data request for a report, and the ACT! data provider processes this request and returns a set of data. In this case, the ACT! provider is not able to handle this single data request, so we can have Query use several smaller data requests instead.

  • Edit the report.
  • Click the Advanced button in Step 2 of the Report Wizard. This brings up the Customize Report Wizard.
  • Use the Next button to reach the "Specify BeforeData Code" step.
  • In the BeforeData code box, enter this single line of text: SQApplication.DataEngine.PerformJoins = .T.
  • Use the Next button to reach the "Specify AfterData Code" step.
  • In the AfterData code box, enter this single line of text: SQApplication.DataEngine.PerformJoins = .F.

With this done, click the Finish button to close the wizard, and try your report again.

 
Was this article helpful? yes / no
Related articles A message reading "ACT! OleDB Provider for Reporting 2.0 : Undefined column name -name-" appears when running a report.
A message reading "Property CursorSchema has invalid value." appears when running a Stonefield Query for ACT! report.
Adding Fields to Advanced Layout Reports
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.
Article details
Article ID: 24
Category: Error Messages
Rating (Votes): Article rated 3.1/5.0 (73)

 
« Go back