4
UI Issues and Work Arounds

This chapter describes user interface issues and their work arounds for Oracle9i Reports Developer.

4.1 Source Control (Windows only)

To enable the use of Oracle Source Control Management with Oracle9i Reports Developer, you must set a number of registry variables. Oracle Source Control Management provides a Start menu item that will update the registry variables for you:

Oracle 9i Developer Suite-> ORACLE_HOME -> Oracle 9i Software Configuration Manager -> Use as Source Control For Forms/Reports

This menu item runs a file named drsc61.reg. By running this file, you are updating the registry variables required by Oracle9i Reports Developer.

4.1.1 Check In/Check Out Restriction

If you are using the source control integration feature in Reports Builder, you should not select the check out after check in option. Doing so will result in the report being placed in Read-only mode. To avoid this problem, you should always perform check ins and checkouts as separate operations.

4.2 Some Languages Not Appearing Correctly in Web Source View

In the Web Source view of the Report Editor, the following languages may appear garbled: Japanese, Thai, Arabic, and Hebrew. To work around this issue, you can set the font names for Reports Builder in uifont.ali as follows:

[rwbuilder]
.....ja16sjis="MS Gothic"
.....ar8mswin1256="Courier New"

4.3 Find/Replace in Web Source View for Asian Languages Causes Crash

When performing a Find/Replace operation in the Web Source view of the Report Editor and running in an Asian language (for example, Japanese) on Windows, the Reports Builder crashes. This problem does not occur on UNIX.

4.4 Documentation Errata

This section describes known errors or omissions in the documentation.

• If you are looking for information about REP_UTIL_PPL, refer to the Getting Started on the Oracle Technology Network (http://otn.oracle.com/products/reports/).

• The link to the Oracle Express example in the Oracle9i Reports Developer Getting Started is incorrect. The version of the Getting Started available on the Oracle Technology Network (http://otn.oracle.com/products/reports/) has the correct link.

• The PAGESIZE parameter cannot be set from the Runtime Parameter Form. It can only be set from the command line (e.g., rwclient).

• The PAGESIZE parameter's value will be applied to all sections in the report (header, main, and trailer).

• In order to run the barcode example report that is referenced in the Oracle9i Reports Developer Getting Started on the Oracle Technology Network (http://otn.oracle.com/products/reports/) and the Oracle9i Reports Developer Building Reports manual, you must:
  • Add oraclebarcode.jar to the REPORTS_CLASSPATH (for the Reports Builder).

  • Add oraclebarcode.jar to the classPath attribute of the engine element in the Reports Server configuration file (ORACLE_HOME\reports\conf\<server_name>.conf).

• The Reports Builder online help incorrectly states the requirements for Acrobat 4.0 for PDF output. The help states that you need Acrobat 4.0 packs in all cases when you really only need it for font aliasing:
  • If you are building a multi-byte report for multi-byte languages, such as Chinese and Japanese, and you need to alias the font in PDF output, you need the CID fonts named within the Acrobat 4.0 packs. Otherwise, you do not need the CID fonts in the Acrobat 4.0 packs.

• In Chapter 6 of Oracle9iAS Reports Services Publishing Reports to the Web, the method described for generating public and private keys has changed. To generate a new Reports Server key on UNIX, enter the following command:

  $ORACLE_HOME/bin/rwgenkey.sh <public_key_file> <private_key_file>
  
  
  

  To generate a new Reports Server key on Windows, enter the following command:

  $ORACLE_HOME/bin/rwgenkey.bat <public_key_file> <private_key_file>
  
  
  

• In Chapter 3 of Oracle9iAS Reports Services Publishing Reports to the Web, the syntax for the security and destination elements incorrectly describes the securityUserid and portalUserid properties. They should be as follows:

  <property name="securityUserid" value="portal_db_username/portal_
  password@portal_db_connection" confidential="yes" encrypted="no"/>
  
  <property name="portalUserid" value="portal_db_username/portal_
  password@portal_db_connection" confidential="yes" encrypted="no"/>