1181965 - Custom JDBC provider option and Crystal Reports

When using a custom JDBC driver, the custom JAR file has options specified within it to control what is available and can be used with the database when that JAR file is used.

When a JDBC connection is created within Crystal Reports, these options are not being used, why is this occurring with a custom JAR file.

Many properties are implemented differently depending on the JDBC provider referenced, for example with an unknown JDBC provider the following list of properties is generally used.

case DbInfo_CanPushDownSorting :
case DbInfo_CanPushDownGrouping :
case DbInfo_CanPushDownSelection :
case DbInfo_CanPushDownSelectIsNull :
case DbInfo_CanPushDownOrSelections :
case DbInfo_CanPushDownAggregation :
case DbInfo_ExpressionsSupported :
case DbInfo_CanDoSelectDistinct :
case DbInfo_CanShowSqlQuery :
case DbInfo_CanOpenDataFiles :
case DbInfo_CanUseConnectionStrings :
case DbInfo_FetchValuesSequentially :
case DbInfo_CanAttachToRowsets :
case DbInfo_CanExecuteCommand :
case DbInfo_CanExecuteAsynchronously :

There is no method to control which options are being used by Crystal Reports with a JDBC connection referencing a JAR file.

JDBC, JAR, PROPERTIES , 1347527 , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Bug Filed

SAP Crystal Reports XI ; SAP Crystal Reports XI R2