Joseph after Shawn

>>Speedware can be as effecient as you want it to be.

> Maybe it can be as efficient as *you*  want it to be. .....
> As I said earlier, I am not impressed with the "efficiency" of any 4GL.

Maybe by some definitions it is only a "3-1/2 GL", but I will (again)
put in a short plug for Transact/iX:

(1)  Compiles to true NMPRG or put in XL.
(2)  At or near COBOL or C performance for most things, AFAIK.
(3)  Costs a lot less than Speedware and a *lot* less than PH.
(4)  Full-function, fully procedural language.
(5)  Do everything you can with COBOL, using only 10 to 50
      percent of the code (yes:  big range;  usual "it depends" applies).
(6)  With recent enhancement to support IMAGE B-Trees, the
      Transact FIND statement now supports *ALL* IMAGE FIND
      modes (not just the additional B-Tree modes).
(7)  With other recent enhancement, Transact allows import of
      externally generated database and file ID's.
(8)   It has a really good symbolic native mode debugger.


And Transact has another "emerging" advantage:  As the "thin
client" features of QCTerm keep looking better and better, IMO
Transact/iX is an ideal language to use for the server component
of an IMAGE database I/O system using QCTerm as the front
end:  It has a very capable DISPLAY statement, along with very
good data input and string handling capabilities....

My $0.05,

Ken Sletten