Re: Forms 5.0 Generation

The problem resolved by migration to Oracle 7.3.4 or 8.0.4 only I think.

Please read quotation from Developer 2.1 Release Notes:

"... 15.9 Limitations when Connected to a Pre-7.3.4 Database

           The following limitations only apply to pre-7.3.4 databases:

           Problem 1 - PL/SQL Compilation performance may be poor. In some

           cases, the compilation may be greater than 10 times the normal

           compile time. Since PL/SQL compilation only occurs at design

           time, this is not a runtime issue.

           Problem 2 - Connecting and disconnecting may take much longer

           than normal. In some cases it may take greater than 10 times

           the normal connect or disconnect time.

           Problem 3 - When you compile PL/SQL, the schema name becomes

                                                    ^^^^^^^^^^^^^^^^^^^
           bound into the PL/SQL code for client references to stored
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

           program units.  The application can only be run against this

           schema.  Against a 7.3.4

           database the schema is resolved at runtime as in Developer/2000

           release 1.x.  The problem also exists in Oracle8 8.0.3, but is

           resolved with 8.0.4.



           Problem 4 - To make sure that your PL/SQL code executes properly

           against a pre-7.3.2 database, you should refer to section 14.6

           for information about preparing your database.



           NOTE: Because of these problems we *strongly* recommend that you

           develop against an Oracle7 7.3.4+ or Oracle8 8.0.4+ database.

           We also *strongly* recommend that you deploy your applications

           against a 7.3.2 or higher database.

..."

agaldo_at_bbvnet.com wrote:
>
> Thanks for your answers (Zafer and valery) but I think this is not the problem
> that I am having. It is not a database name problem, the database has the same
> name in both environments.
> It looks like Dev/2k is hardcoding inside the fmx some stored procedure
> information that will not match in the new environment. It looks like a Dev2K
> problem, not a server problem, but I am kind of confused...
>
> Could anybody give me more info about this issue? I'd rather get more opinions
> before migrating to another Server version or Dev 2K version.
>
> Thanks again,
>
> Antonio Galdo
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> http://www.dejanews.com/ Now offering spam-free web-based newsreading

-- 
Valery A. Sorokin
ProSoft, Russia, Moscow