Gibson just said:

> Any thoughts on migration options for the Transact programming
> language?

As a practical matter, IMO users with complex multi-user Transact
systems that want / need to "migrate" to something else are effectively
faced with recoding from scratch;  I doubt there are or will be any
"automated" tools that can significantly reduce that effort..  Of course
if your in-house team is familiar with the business logic currently
embodied in your Transact code, you have a big leg up..

And continued:

> I was asked if Image will run on other platforms.  I said no
> because I had never heard of anyway to let Image run on anything
> except an HP e3000.  Then I was reading the following web page:
> http://www.interex.com/tech/3000/e3000migration.html
>
> When I came across this item:
> Database:              HP-Eloquence: HP Eloquence
> (www.hp-eloguence.com) is a TurboIMAGE clone that runs on
> UNIX, Linux and Windows NT/2000. It is supported by Marxmeier
> Software (www.marxmeier.com).

You might want to contact Charles Finley (if he doesn't respond
directly after reading your message...  :-)  ).  He is very familiar and
has long experience with HP-Eloquence, migration options, etc.

> .....  If we migrate can we use the same structure and data?

I don't even begin to be an HP-Eloquence expert, but as far as the
data structures in your TurboIMAGE database and IMAGE intrinsics,
I believe the answer is essentially "yes".....  Unfortunately, your
Transact code will never run on UNIX - Linux -Win2K (except (maybe,
if HP facilitates the effort) ) under an MPE emulator running on top of
Linux)....

Ken Sletten

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