The best thing (IMHO) HP could do here is to update Allbase/SQL to the
most recent SQL-9x standard and bundle it in with Image (both on new
systems as well as older ones still under maintenance).  Bump up
the support costs if you have to, but give the users both a Network
and Relational database engine as part of the standard package.
From that point on, the users would be free to develop/port their
apps into whichever architecture is appropriate.  Stop trying to
make Image into something that its not.  It's not a RDBMS, and
never will be, regardless how much fluff is added over the top.

Respectfully,
Michael L Gueterman
--


-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Mark Boyd
Sent: Wednesday, March 07, 2001 12:02 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Expensive RDBM Systems (Oracle)


These are functions of a data entry application, NOT a dbms.

"Input masking, value limits, non-structural data
validation"

-----Original Message-----
From: James B. Byrne [mailto:[log in to unmask]]
Sent: Wednesday, March 07, 2001 9:38 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Expensive RDBM Systems (Oracle)

On 6 Mar 2001, at 13:40, Wirt Atmar wrote:

> What features do see lacking in IMAGE?
>

Input masking, value limits, triggers, non-structural data
validation, field overlays, composite key fields, and a few others
that I can't bring to mind.   Admittedly most if not all of these can
be designed around or dealt with satisfactorily by a good data-
dictionary based programming environment like Powerhouse, or
Transact, or Speedware.  However, choosing one of these products sort
of limits your programming options.
<snip>