Re: Forms5 against multiple DBs

From: Marcel Claus <Marcel.Claus_at_Informatik.Uni-Oldenburg.DE>
Date: Wed, 27 May 1998 15:41:16 +0100
Message-ID: <6kh54v$mgh_at_news.Informatik.Uni-Oldenburg.DE>


Jamie Keir wrote:

> Hi.
>
> I have a form which uses DBMS_SQL package. In previous releases (ie 4.5)
> I could compile this form agains a 7.1.6 DB and run it there *and*
> against a 7.1.4 DB. I didn't try it the other way round.
>
> Under Forms5, it seems it needs to be compiled for each DB revision,
> otherwise Forms complains of ORA-04062 : timestamp of DBMS_SQL has been
> changed.
>
> This, as you may guess, is a *major* pain in the arse; and so, on to the
> question:
>
> Does Forms5 insist on all forms being recompiled for a new DB version,
> or is it just being picky about DBMS_SQL?
>

I think this is a new FEATURE of Dev2k V 2.0 (Forms 5.0). Thereare some things I'll never understand:
- Why the fuck do you have to recompile your damn forms 5.0 app   every time you change the database you run your app again?????? - Why the fuck do you have to recompile your Report 3.0 reports   every time you copy it to another computer ???????? (I always   get the error message: "unable to retrieve a string from the report   message builder" or something like that) This really sucks. I have more than 30 clients and recompiling every report I change on nearly half of the machines (sometimes copying the executables works, but I don't know why, it's non-deterministic). I hope this will change with Dev2k V2.1 or someone gives me the documentation for the report-nodes under forms 5 and a docu for the run_report_object procedure. The ORACLE-hotline (Germany) said that this is a know bug and that you can't do anything except recompiling your app.

Marcel Received on Wed May 27 1998 - 16:41:16 CEST

Original text of this message