This will be as a result of the way in which the ODBC connection is setup on your system. Note that when running crystal reports, it is the user specified in the ODBC connection that is used to actually run the report at a background level). Please check your ODBC as follows (note that you may require the assistance of your IT department to check and change this connection):
Ensure that the ODBC connection is set up as a 32-bit System DSN
Ensure that the ODBC connection type is set to SQL Native Client xx.xx (where xx.xx is the relevant version number)
Ensure that the user specified in the connection has relevant permissions on SQL to access the database (note that if the connection is set as Windows Authenticated this will not usually have sufficient permissions unless your Dimensions logon is also Windows Authenticated).
It may also be caused by the version of the Crystal Print Engine used on the computer. You can find the current version via the About Dimensions screen and select the System tab. Compare the version of the Crystal Print Engine to a computer for which the reports are printing OK.