Hi Kelley,

Is this happening on other reports?

Here is an article I came across - http://kb.sageintelligence.com/index.php?title=Error:_%22ODBC_SQL_Server_Driver_DBNETLIB_ConnectionOpen_(Connect())._ODBC_SQL_Server_Driver_DBNETLIB_SQL_Server_does_not_exist_or_access_denied

Hi Chloe - It sounded promising.  I did not have the Named Pipes enabled so I made that change.  The report still throws the error.

I do, however, have another clue.  The report works perfectly using the Sage 300 Sample Data.  The PJC project in Sample data is using a Contract Style: Standard.  The database I am trying to run the report with uses a Contract Style: Basic.  

It appears as if the report will not work with a Contract Style: Basic.  Darn!  I was so hoping i could take advantage of the work that had already been done.  Back to the drawing board.  *sigh*

Thank you for your response.

Resolution

Problem:  Mixed ODBC

Resolution:  

In the Report Manager, go to Home, R-Click and look at the Tenant Cache Viewer.  When I did this, I saw most of my connections were using the SQL Server Instance Name.  I had a couple that were using a different ODBC.  In my case, the company I was trying to run reports for was using an ODBC that was different than the Server Instance Name.  

I went back and from my Home, R-Click and chose the option to "Clear All Cached Connection Information".  I then went to my ODBC setup for this company in database setup.  Changed it to be the Server Name.  When I went back into the Company and Report Manager, everything then worked.  The Connection information was correctly added automatically.

this is awesome - it helped me with my issue - thank you so much