Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AR Invoice and sub reports

Status
Not open for further replies.

Deborahza

Technical User
Jan 16, 2009
17
GB
Hi,

The ARDINVO report was modified to add optional fields on a sub report by a old colleague.
Saved a copy, re-set the datasource locations on the main and sub report.
When I run the report in crystal it brings back the invoices but when I run it through Accpac I get "The table 'ARIBDO' cannot be found. If I delete the sub report - it runs through Accpac so I'm assuming it has something to do with the links. Any idea's?

TYIA
Debbie
 
It's MSSQL 2005 and A4W5.5
And using Crystal 11
 
How are you adding the table to the report? You'll want to use the way driver that the main report uses otherwise Accpac might not be able to change the path when it invokes the report.
 
Ok I made a boo boo, it's 5.6
It's on the test server we are using to test the 5.6. upgrades and integrations to our fuel system.
The main and sub report are using the same ODBC driver. We have tried running just the sub report with only the ARIBDO table and we still get the same error.

TYIA
Debbie
 
I have tried running it on my laptop now and it works. So I am re-installing AR on the 5.6 test server and will see if that makes a difference.

 
Are you using the version 5.5 report with version 5.6?
 
No. It's the ARDINVO report in the 5.6 folder that has a sub report added.
Ran a repair on the Accpac instead of re-installing and it still gives me the error on our server. Yet it works on my laptop through crystal and Accpac.
 
If I do copy it into 5.6 and use it, get the same error
 
It can only be something you are doing wrong, I've added subreports to 100s of these reports without any problems. Without seeing your report it would be almost impossible to say what is wrong.
 
Ditto here. You're making a basic mistake, like using OLE instead of ODBC.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top