Re: Why Oracle Tools?......
Date: 1995/12/09
Message-ID: <enduser-0912952049130001_at_204.247.5.19>#1/1
Oracle Power Objects all by itself is a real nice gui and reports generator.
by the way, Visual Basic has no native tools for dealing with a database! worse, it has no after market vendor making anything like you need when trying to get screens up and running agains tables. you will spend plenty of hair pulling making a database gui with vb.
even oracle enterprise tools like forms are superior to vb in this regard.
also, vb is not cross platform, oracl is on all levels.
In article <4a3isi$km4_at_bingen.hrp.no>, jensr_at_hrp.no (Jens Roynlid) wrote:
> tluers_at_one.net (t) wrote:
> >I'd love to hear your two cents worth to the folowing question:
> >As a development environement that uses an Oracle server, why should I
> >choose Oracle tools (Forms, Reprts, etc...) for my front end? Why not
> >Delphi, Forte, VB, or others?
>
> I could give you some reasons why you should NOT choose Oracle tools:
>
> 1. Oracle doesn't support Windows 95 or Windows NT. (They may run, but
> try to ask Oracle support for help with any problems - they'll turn
> you down immediately.)
>
> 2. The Oracle tools support only Oracle databases natively.
>
> 3. The UI produced by Oracle tools is generally unacceptable (lots of
> quirks).
>
> 4. There are lots of limitations in the Oracle tools (e.g. error
> messages cannot have more than 100 characters).
>
> 5. When you deploy applications written in Oracle tools, you'll get
> lots of technical supprt questions because of UI intricacies, product
> instability, etc.
>
> 6. Error messages produced at runtime are cryptic and difficult for
> users to understand.
>
> My advice: forget Oracle tools, use VB or Delphi. They're modern,
> flexible and extensible tools and support several different
> databases.
>
> All opinions expressed here are mine, and not necessarily my
> employer's.
>
> Regards,
> Jens R.
Received on Sat Dec 09 1995 - 00:00:00 CET