Re: PowerObjects vs. PowerBuilder: pros & cons

power objects and oracle media objects can make anything youll need. the so called large scale project is just an excuse to have too many hands in the pot, and usually endus up in a mess that never hits the screens.

use opo to get your stuff done, youll get an integrated reuport writer to boot.

---

In article <4fq2to$5v5_at_pheidippides.axion.bt.co.uk>,
rmoulding_at_bibbway.bt.co.uk (Richard Moulding) wrote:



> Power Objects is Oracle's VB beater. Aimed at building office sized 


> applications, so fits in nicely with the Workgroup/2000 database. Like VB it 

> may not scale too well. (Oracle will hate this: Card for the 90s?).

> 

> Forms 4&1/2 (& Reports) is aimed at corporate applications. Usually for

 mid to 


> large scale development teams. Handy if you want to use the CASE products 


> (Designer/2000).

> 

> Regards,

> 

> 

> 

> In article <4fn5go$p0m_at_falcon.ccs.uwo.ca>, deng mei <mdeng_at_julian.uwo.ca> 

> wrote:

> >Thank you for your reply.

> >

> >I still fail to understand. Access and FoxPro are database, like Personal

> >Oracle 7; PowerObjects is development tool, like VB.

> >Whether PowerObjects is competitive with PowerBuilder is an interesting

> >issue. I hope you have more opinion.

> >Another issue is: what is the difference between PowerObjects(as part of 

> >Workgroup/2000) and SQL*Forms/Reports(as pars of Developer/2000)?

> >I just begin to learn Oracle, so I an confused by so many "2000".

> >

> >Thank you very much for your time.

> >

> >mdeng_at_julian.uwo.ca

> >

> >

> 

> Richard Moulding

> BT

> rmoulding_at_bibbway.bt.co.uk

> My views, not my employers'