Re: PowerObjects vs. PowerBuilder: pros & cons

How do you know that our large scale developments are 'just an excuse to have too many hands in the pot'? (whatever that strange metaphor means).

You'd probably build your company's billing system in OPO or VB, right?

Large projects, with multiple inter-dependencies, many screens and thousands of users are a fact of life. Washing your hands of them using such glib statements (and spelling mistakes) is derisory.

But I'm sure you meant well.

Regards,

In article <enduser-1402962011550001_at_dial-sc1-1.iway.aimnet.com>, enduser_at_enduser.com (EndUser) wrote:
>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).
>>

Richard Moulding
BT
rmoulding_at_bibbway.bt.co.uk
My views, not my employers' Received on Tue Feb 20 1996 - 00:00:00 CET