1. Ensure you created your report using an ODBC connection and the sa user / password.  

2. Ensure the option to Save Data with Report is NOT selected

Since v2012, Sage 300 Crystal Runtime has had issues running queries that include items not in the data dictionary. This does include views. The work around I typically implement to get around this is to implicitly reference the view using a sql command, "Select * from <viewname>". In crystal designer you can go to Database>Set Datasource Location in order to update your view properties to be a command.

1. Have used ODBC and same password for this and all other working reports added for past 6 years

2. Definitely do not ever SAVE DATA and have confirmed that this is NOT selected in this particular case.

Hello Angel G, I have found the spot to add command under ODBC.  Is there a trick to setting parameters?  First I get "Failed to retrieve data from database" then "Invalid argument provided".  Tx, G

hmmm....You should be able to just use parameters as normal if your command syntax is "select * from <viewname>"

Here in Set Datasource Location you can update a data element like a table or view to be a command. First click on your view name in the top portion of the screen, open your connection in the bottom portion of the screen, click Add Command then Update.

Another option we have gotten to work is to save your report to use a Trusted Connection. This option is not my favorite because then you have to create a sql user with read access for whatever windows user(s) that will run the report.

One other thing to try - ensure that the left-most table in your report is a true Sage 300 table.  You could for example use the CSCOM table, ensure you add the AUDTORG field to your view then link the CSCOM table to your view on the AUDTORG field.

I have switched around the files around so that the CSCOM file is my first table with a left enforced join to my view. Unfortunately, I still get the error "unable to load" when adding the report to the Accpac Reports menu and it still isn't generating output when run from the menu but runs without issue from Crystal Reports.

Hi, I've set up command as datasource.  I was able to add the SQL successfully and swap out all references to the original view.  When I attempt to view the report in Crystal I get the following error:

Any idea how to get around this?

Thanks!