SAP Knowledge Base Article - Public

1213080 - Exporting to ODBC causes Crystal Reports to terminate


  • Crystal Reports crash.
  • When exporting reports with many database fields, to ODBC, Crystal Reports stop responding.
  • Able to export other reports with less fields to ODBC successfully.


  • SAP Crystal Reports 2013
  • SAP Crystal Reports 2016
  • SAP Crystal Reports 2020

Reproducing the Issue

  1. In Crystal Reports, open a report with many database fields.
  2. Export the report to ODBC
  3. Crystal Reports crash. 


  • Report containing more than 254 objects causes Crystal Reports to crash when exporting to ODBC data source.
  • In more details:
    • Crystal Reports fails to export to an ODBC data source because the export attempted to create more fields in the database than the database supports.
    • When exporting a report to an ODBC data source, a table is created in the database and within that table a field is created for each object in the report. If the number of objects on the report exceeds the number of fields that can be created within this new table the report will fail to export and Crystal Reports will stop responding.

    • The maximum number of fields for a table is dependent on the database type itself. Report Objects include:
      • Database Fields
      • Text Fields (Including column headers)
      • Charts
      • OLE Objects
      • Picture Objects
      • Cross-Tabs
      • Subreports
    • For example:
      The maximum number of fields allowed within a Microsoft Access table is 254. Exporting a report containing 255 or more objects to an Access ODBC data source will fail.


  • To be able to export the report to ODBC, remove objects on the report, so it contains 254 objects, or less.


CR, crash , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Problem


SAP Crystal Reports 2013 ; SAP Crystal Reports 2016 ; SAP Crystal Reports 2020