Re: Designer/Developer

Hi,
[Quoted] Designer and Developer are tools of different purpose and weight. Roughly speaking:
[Quoted] Developer is to create end-user interface to Oracle (and others, but I never tried) database.
[Quoted] Designer is to support entire application development process virtually from [Quoted] the very beginning (requirements analysis) to the very end (application implementation and post-implementation support). To use Developer, you can have no idea of analysis and design techniques, [Quoted] information and process modelling, and so on. You can use the power of Designer without having to generate Forms application at the end of the process.
So, it depends on your purposes. If you have to develop Forms application in [Quoted] [Quoted] a short time, and you already have database, - use Developer. If it is a complex project involving analysis, DB design, hundreds of tables, forms and [Quoted] stored procedures - you should think of using Designer. Regards,
Eugene.

Sylvie Picouet <s.picouet_at_free.com> wrote in message news:IqLv4.9$PE7.52276_at_nnrp3.proxad.net...
> Hi,
>
> A project is going to start with Oracle/forms.
> And we wonder if we should start with Designer and then work always from
> Designer to Developer, or just work with Developer?
> If someone could send me some information about his experience with
> Designer...
>
> Designer Repository seems to be cumbersome. Does the Database Design
> Transfert work well, even with iterative steps ?
>
> Thanks,
>
> Sylvie.
>
>
>
>
Received on Fri Mar 03 2000 - 00:00:00 CET