From our brief acquaintance testing eloquence, the dbms access seems very
good, excepting the already mentioned lack of partial lists of fields to be
read/written/updated. ie, only @ item lists are supported so far. C code
reading Image on MPE will move across almost untouched.
Unless you know some form of basic, the bundled dev environment will be very
foreign to you. There is a sort built inside it, so that will help some.

Is powerhouse not on UX already in a suitable form?

jp
----- Original Message -----
From: "James B. Byrne" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Saturday, February 14, 2004 9:36 AM
Subject: [HP3000-L] HP Eloquence and Business Basic


> I am once again on my annual quest to examine migration options for
> our Powerhouse based system.  This time we are looking at HP
> Eloquence.  The ease of data conversion looks quite appealing but I
> am wondering if the development language that ships with Eloquence
> is suitable for rewriting our Quick/Quiz/QTP code and whether or not
> this is a wise idea.  Comments? Opinions? Case histories?  Are there
> strong reasons to just use Eloquence as a DBM and develop in
> another language, presumably using an ODBC driver to access the
> data?
>
> Thanks in advance.
>
> Regards,
> Jim
> --
>      *** e-mail is not a secure channel ***
> mailto:byrnejb.<token>@harte-lyne.ca
> James B. Byrne                Harte & Lyne Limited
> vox: +1 905 561 1241          9 Brockley Drive
> fax: +1 905 561 0757          Hamilton, Ontario
> <token> = hal                    Canada L8E 3C3
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *