Re: Designer 2000

We have just completed an application with the majority of server and client side code generated to Oracle Forms 5.0. The biggest benefits of Designer deployed apps comes when the maintenance programmers have to deal with the "aftermath" of an application. The code that comes out of Designer is incredibly consistent and clean...which makes maintenance MUCH easier.

To make life easier on yourself, however, learn EVERYTHING you can about Preferences for whatever generator you are going to use and how to implement them, build a good object library (since many of the Preferences are being replaced by them anyway) and build a solid template. The template is becoming more and more of a "container" rather than a place to put code - but it still needs to be tested and solid. Freeze the preferences at the application level after enough Forms have been generated that you are reasonably satisfied with their appearance...let developers make changes at the module level if they *must* present something a different way. Keep your code in Designer - it makes no sense to keep it outside - it just makes maintenance harder - and when/if the app is regenerated you are likely to run into synch problems with code maintained outside of Designer.

Document ALL of your changes in the Repository if you make any post-generation changes to the Forms..and try to keep them to a minimum...also, BIG ONE, make sure your non-Designer developers know how to enter any custom code around the CASE-generated code to prevent it being written-over the next time the application/Form is generated..! (I've seen grown men cry over this one...<g>...especially when it wasn't documented in the first place!!!)

We ran Des 2.1.2 on Oracle 7.3.4 - we had to do major tuning during the generation phase - until we increased our rollback segs we were bouncing the database once a day...so, don't forget to tune the Repository...

Hope this helps!!!!

Chana Campos

Sambavan Tharmarajah <sambavan_at_cs.utexas.edu> wrote in message news:Pine.LNX.4.10.9906010759160.21986-100000_at_rattlesnake.cs.utexas.edu...
> On Mon, 10 May 1999, S,Erik wrote:
>
> > Is anyone using Designer/2000? If so...
> >
> > Are you having any problems with generating, or have you chosen not to
use
> > that part of the application?
> Yeah, it is at times painefull to work on it. But I have been developing
> oracle web forms for the last 2yrs, using the stored procedures and
> functions. It was not much problem. If you are using web server
> generator, then it is painful.
>
> >
> > What versions are you using?
> >
> V7.3.2
> > Are you generating Oracle Forms? Web pages?
> >
> Web pages.
>
> > Are you generating modules more complex than a data entry form?
> Yeah.
> >
> > What would you say are its best and worst features?
> >
> Its webgenerator will look for names terminating with $ sign and another
> synonym with $ sign. If you figure out that it will be more convenient to
> generate standard forms. I all ways prefer to use its stored procedures
> the
> > How would you rate Oracle's support of the product?
> Pretty good.
> >
> > Thanks,
> >
> > Erik
> > e_at_technologist.com
> >
> >
> >
> >
>
> Sam .T
>
> 600 West 26Th Street, Phone : (512) 474-2328
> Apartment #E 144, E-mail: sambavan_at_cs.utexas.edu
> Austin, sambavan_at_mail.utexas.edu
> Texas - 78705. sambavan_at_tenet.edu
>
>
>
>
> -------------------------------------------------------
>
> You should treat all disasters as if they were
> trivialities but never treat a triviality as if
> it were a disaster
>
> --- QUENTIN CRISP.
> --------------------------------------------------------
>
Received on Wed Jun 02 1999 - 14:44:42 CDT