You didn't indicate how you are running this report.  Was the report added to the report menu in one of the Sage 300 CRE modules?  If so, which module?  And if you are running it from one of the accounting modules, do you have the tsDesignMode formula on the report?  If you have it on the report already, are you running the report in Standard Description mode?  (The tsDesignMode formula would contain "SDesc" if that is the case).

Also, in your Sage 300 CRE file location settings (Common Tasks - File - Company Settings - File Locations), scroll all the way down to the "Reports" path and verify that the machine (and Windows user) that is having issues has access to read files in that path.

Also check to make sure that you don't have the "Save Data with Report" option selected in the File menu of the Crystal Report design (it doesn't sound like this is the issue, but it's worth checking anyway).

And since this is a custom report, did you use any SQL queries with embedded parameters in your design?   And if none of the above helps in solving the problem, could you please cut and paste your Record Selection formula here so we can see it in case that can give us a clue as to what's going on?

A lot of questions, I know, but we need more information.

Hi Gary,

- the report is being run from the report menu (Accounts Payable>Reports>Customer>"Report Name")

- I did not have the tsDesignMode formula in there but I added it and we're still having the same issue with the 1 computer.

- We are running it in Standard Description mode.

- The user DOES have access to the read files in that path

- It does not have the "Save Data with Report" option selected

- Here is my record selection formula:

{APM_MASTER__INVOICE.Invoice_Date} in Date ({?From date}) to Date ({?To Date})

Hope this is enough information, appreciate the help :)

Hi Kprinse,

What version of Sage 300 CRE are you currently using?

18.2

Thinking of things that would only affect one computer - I would check the ODBC DSN configuration to make sure it's setup the same and has the same accounting folder assigned.

Also if you are on 18.2.1 there was an ODBC hotfix that may need to be applied to the 4th workstation. If you are on 18.2.2 then it's already included.

If none of that makes a difference I would have one of the users who's report is working login to Sage on this 4th computer to see if the problem persists.

I might also check the Windows date formats to see if any set to MM/DD/YYYY or DD/MM/YYYY.

Yes I've checked the ODBC DSN configuration and actually removed and set it up again and still the same issue. We are running on 18.2.2, the Windows date format are the same on all computers. I've logged in with antoher login and it is the same issue on that 1 computer. Only thing that I can think that is different from all the other computers is that they are running on Windows 7.

Yes I've checked the ODBC DSN configuration and actually removed and set it up again and still the same issue. We are running on 18.2.2, the Windows date format are the same on all computers. I've logged in with antoher login and it is the same issue on that 1 computer. Only thing that I can think that is different from all the other computers is that they are running on Windows 7.

I'm presuming your date parameters are configured as dates.  Maybe, is your Select Expert statement producing a confusing result because it's changing a  'machine/database' date into a differently-formatted Crystal date that uses 'other than US' formatting?

Try not converting a date into a date by simplifying your Select Expert statement to this: {APM_MASTER__INVOICE.Invoice_Date} in {?From date} to {?To Date}

Thanks for the suggestion! I ended up doing that and it resolved the issue.