title: ODBC Connection / Crystal Reports
body: <p>We have some VERY old Crystal 8.5 reports (slated for re-write in Crystal 2016 this year), which have stopped working yesterday. They use Crystal Query (<code>.qry</code>) files as their data sources running against an Oracle Database 12c (12.2.0.1.0) database.</p>
  
  <p>When we run the <code>.rpt</code> file in Crystal, the reports run forever until we get out of memory issues albeit the data they return is gobbledygook and the number of pages (tens of thousands) bears no relation to the expected results.</p>
  
  <p>When we run the <code>.qry</code> files in Crystal SQL Designer 8.0, we get only the first row of data returned.</p>
  
  <p>Turning on tracing in ODBC Data Source Administrator, there are a couple of entries in the log file that seem to indicate a potential issue:</p>
  
  <blockquote>
  <pre><code>test            f3b4-f974   ENTER SQLSetConnectAttr 
      SQLHDBC             0x023ECB78
      SQLINTEGER                1041 &lt;unknown&gt;
      SQLPOINTER          [Unknown attribute 1041]
      SQLINTEGER                  -3 
  
  test            f3b4-f974   EXIT  SQLSetConnectAttr  with return code -1 (SQL_ERROR)
      SQLHDBC             0x023ECB78
      SQLINTEGER                1041 &lt;unknown&gt;
      SQLPOINTER          [Unknown attribute 1041]
      SQLINTEGER                  -3 
  
      DIAG [S1C00] [Oracle][ODBC]Driver not capable. (0) 
  
  test            f3b4-f974   ENTER SQLSetConnectAttr 
      SQLHDBC             0x023ECB78
      SQLINTEGER                1042 &lt;unknown&gt;
      SQLPOINTER          [Unknown attribute 1042]
      SQLINTEGER                  -3 
  
  test            f3b4-f974   EXIT  SQLSetConnectAttr  with return code -1 (SQL_ERROR)
      SQLHDBC             0x023ECB78
      SQLINTEGER                1042 &lt;unknown&gt;
      SQLPOINTER          [Unknown attribute 1042]
      SQLINTEGER                  -3 
  
      DIAG [S1C00] [Oracle][ODBC]Driver not capable. (0) 
  </code></pre>
  </blockquote>
  
  <p>If we use a third-party viewer, we are able to generate most of the reports. If we run reports that don't use a <code>.qry</code> file, we don't have any problems. </p>
  
  <p>Has anyone ever come across a similar issue? Or does anyone have any pointers on what could have changed that we are not aware of as a result of any patches etc?</p>