HP3000-L Archives

March 2001, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Richard Gambrell <[log in to unmask]>
Reply To:
Richard Gambrell <[log in to unmask]>
Date:
Tue, 6 Mar 2001 21:08:33 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (79 lines)
Wirt Atmar wrote:
>
> Donna writes:
>
> > - richard is absolutely right -- with how the computer industry has
> >  evolved, mpe is a genuine bargain these days.  but without a more modern
> >  database, who's going to use the platform?  it's more than time for another
> >  database solution.  i wish i had an answer for what that solution is.
>
> What features do see lacking in IMAGE?
>
> So far, I haven't found anything I can't do in IMAGE -- at greater efficiency
> and with less cost (both in development time and real dollar maintenance)
> than I can in any RDBMS.
>
Some ideas...

Some well designed java object models that encapsulate Image calls
for an actual database into easy to understand and resilient methods
might help (I think Mike Yawn is already working in this direction),
but this really isn't enough to the SQL trained.  Having to code
your way through the minutia of using Image to do what a moderately
complex SQL where clause expression can do for you is painful, at best,
and error prone.

The Cognos Powerhouse tools provided a set of simplified methods to
code Image. You didn't need to learn about migrating secondaries
to delete entries from a Master.  That is the kind of Image interface
we need.  You do need to remember what items are indexed to
build powerhouse linkages (equiv. to the SQL where), but that
is true for the mature SQL programmer, too.  I want what Powerhouse
did, but in a GUI/Web/Laser world.

I'd love to have tools to be able to do three things with Image:
1) Provide a smart data entry form with GUI type features for
the casual user by using some visual tool that helps layout the
form, build lookup selection lists, and by simple coding (e.g. SQL)
of relationships and editing rules.  It needs to be able to
take that data and update the appropriate datasets when the
user leaves that logical transaction (or upon an explicit save).

2) Build reports using a similar tool to #1

3) Build web pages with a web design tool with integrated objects
that and put and return database data, given simple (e.g. SQL)
coding and editing rules (like #1 and #2 combined).

Obviously, it isn't the visual aid for design, but the database
updating and editing language that matters here for interfacing
to Image.

These tools would need to be used by enough developers to build
a shared community of ideas and expertise, and be backed by
a company that is going to be around. The more these tools are
built around stable languages (like SQL or even Java), the
better.  There is little need to reinvent the language wheel.

Finally, I need these tools yesterday, but they can't cost
very much.  How much does it cost to use SQL-server and code
in VB and Access, or Delphi, or whatever.  I do think the
industry in general is still missing the boat on Web database
application building tools.

Richard

> Wirt Atmar

--
Richard L Gambrell, Director of Computing Systems and Networks
Information Technology Division
University of Tennessee at Chattanooga
103 Hunter Hall, Department Code 4454
615 McCallie Ave., Chattanooga, TN 37403-2598
voice mail/cell phone: 423-432-5122
private e-mail: [log in to unmask]
UTC fax: 423-755-4150
UTC phone: 423-755-4551
UTC email: [log in to unmask]

ATOM RSS1 RSS2