I am presuming that this is either an OE invoice or an PO purchase order spec that will not run?  Have you tried other forms and specs other than these two types? 

Call the developer, that's a screwy way to do a report, and Sage 300 can't handle it if it's not ODBC.

This is a leads report from CRM.  Not OE or PO.

Then you can't run it from Sage 300.

I didn't build this report and I work in Crystal almost every day.  The part that bugs me is it worked before and the DSN file appears to have what's needed.

OK.  Do you know if this report is a datapipe report or not?  I don't use CRM to be able to answer this question.  If it is a datapipe report you may be able to copy the config file for that module from another computer that it does work on over and see if that works.  For us, we have to comment out the OERPT.ini for the OEINV01 where it says type=DATAPIPE. 

Not sure if this is the same idea of a situation here or not.  Or if the ODBC DSN's were installed correctly on the new install which can also affect the datapiped reports as well as other things.

Sorry, that is all I have.  If neither of these help, I hope someone else can help you.

Hi Jody,

I really appreciate your help and it sounds like you've learned a bit about the reports in Sage 300.  I know what a datapipe report is and how to deal with them.  This report reads the CRM database which is NOT a Sage 300 database.  Ordinarily, a report that reads a non-Sage 300 database will not work inside of Sage 300. There are ways around it but this customer has one I've not seen before.  I can fix this but I don't understand why it worked before on the previous workstation and not now.

Once i get this done I'll share what I did.

Often it's a sub report that hasn't been verified so it can't find it and causes issues, try that.
Also once had an issue with certain users not having rights to the SQL server database and that caused this error but usually it's a sub report that isn't connecting to the database properly.

Hi Dana, is it also a new user? If it is the user should be added to the SQL user security with read rights.