I've seen this before, but usually with custom reports.   Unfortunately, I don't remember exactly what I did to fix it.

Appears that you are getting this with standard reports?   If so I would start

by uninstalling and reinstalling the workstation.

Thanks Thomas.

Yes it is happening to standard reports that have not been customized.

One thing I did try was to reinstall the 64-bit ODBC driver and that seemed to work on one workstation. On another I unchecked "Use C/S ODBC Driver" in user maintenance and that seemed to work as well.

Do you know why these ODBC issues come up?

Hi,

If unchecking use "Use C/S ODBC Driver" clears the issue - the path to the CS ODBC driver is incorrect or the CS ODBC driver is not running.  

On the server verify that the ODBC service or ODBC application is "running" and pointing to the correct directory\path ..\MAS90\Home\pvxiosvr.exe

From the workstation Sage 100 ..Launcher| Setup | System Configuration | ODBC Driver |

Verify the Server Name and Port

<<Do you know why these ODBC issues come up?>> Usually because the servers are moved\security settings changed or the ODBC driver is not running or pointing at an incorrect path....

Just FYI - All framework Sage 100 reports use the MAS 90 4.0 ODBC x86 (32 bit) driver. The x64 driver is strictly for 3rd party access to the Sage 100 data.

Thanks

John Nichols

Sage