1214999 - Limitations when using crdb_javabeans.dll to report off Java Beans

What are the known limitations when using Crdb_javabeans.dll to report on Java Beans as data sources?

• The following is a list of known limitations when using Crdb_javabeans.dll to report on Java Beans as data sources:
  • 'Float' data types are limited in range from -1.79e+38 to 1.79e+38
  • 'TinyInt' (unsigned: 0-255) in SQL and 'Byte' (signed: -128-127) in Java cannot map to each other unless a conversion function is written to map these data types
  • If data in the database table is not matched exactly for the entered parameter value, a Query Engine Error will be returned
  • Binary and VarBinary data types both return Empty sets; however, the LongVarBinary data type works as expected. This issue is tracked under Track ID ADAPT00081550 (Closed - Not a Problem)
  • Crystal Reports 9 cannot support JDBC reports that contain either Char8000 or VarChar8000 fields. However, JDBC LongVarChar (text) fields containing 8000 characters work as expected. This issue is tracked under Track ID ADAPT00081571 (Closed - Not a Problem)
  • Some JDBC decimal (money) field data has a slight rounding difference when compared with results using an ODBC driver. For example, using the value 922,337,203,685,000.5, ODBC will return 922,337,203,685,001.00, while JDBC will return 922,337,203,685,000.00. This issue is tracked under Track ID ADAPT00081585 (Postponed)
  • Input parameters cannot be set to Null for stored procedures. The "set to Null value" check box is not available in the user interface. This issue is tracked under Track ID ADAPT00082029 (Postponed)

Crystal Reports 9 Creating a Java Bean to use as a Data Source

RAS9 JAVA BEANS CRDB_JAVABEANS LIMITATION ROUNDING Crystal Reports Java Bean data sources Limitations , c2011653 , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Bug Filed