Table Column Ordering Matters when using Forms6i

Question

Just an FYI on something strange that we encountered...
We have a Forms application that calls a function within a Package stored in the database. The only parameter to the function is a PL/SQL record that is based on the columns of a table. Our users need to run the application against 2 different database instances. We receve an "ORA-04062: Signature of Package has changed" error message when running the Form against the database that we DID NOT compile the form against. The reason is because the column ordering of the table that the record is based upon is different between the 2 databases.
Here are the details:
Setup:
     2 different databases. ( devDB and prdDB )
     1 table:
          On devDB:
               create table test_file (file_id NUMBER,
description VARCHAR2(256)
          Same table on prdDB but with different column ordering:
               create table test_file (description VARCHAR2(256),
file_id NUMBER
     1 database package in both databases:
CREATE OR REPLACE PACKAGE PS_TEST AS
     SUBTYPE tr_file IS TEST_FILE%ROWTYPE;
     FUNCTION Create_File( r_file     tr_file ) RETURN NUMBER;
END PS_TEST;
     1 Oracle Form that fills the tr_file record with data and calls PS_TEST.Create_File passing in the tr_file record.
Results:
     If the above Form is compiled on the database devDB, trying to run the Forms Executable against prdDB will generate an error message stating: ORA-04062: Signature of Package has changed. If the above Forms executable is run against devDB, everything works fine. The problem is that when the Oracle form is compiled it apparently captures the tr_file signature from the package, which would be something like ( file_id, description ) on devDB since it is specified as %ROWTYPE. When this compiled form is ran against the prdDB database, the package signature is different because the tr_file signature would be something like ( description, file_id ) on prdDB because of the column ordering. The error doesn't occur if you recreate the "devDB" table with the columns in the same order as "prdDB". This would only be a problem with using the %ROWTYPE with PL/SQL records.
So it appears that column ordering does matter in some situations.
Thanks.

Answer 1

would create a cell renderer only once -- the same
JTextPane is used to render any cell in the table that
shares the same renderer.Thanks for the reply. It's something I'm going to look into, but I do create only one renderer, and use that one renderer to create new JTextPane subclasses when getCellRendererComponent() is called - hence, there is one renderer, but there are multiple instances of the actual rendered component.
In the meantime, I'm just marking up the text with HTML to create the presentation I want, and it works okay. It'd be nice if I can get it working with Styles, though.
Thanks again,
- Chris