One very important example: In Allbase you can define a view to join
several (many!) tables. We use that to present the result of a
complicated selection to the user. By using the view you can make the
server do all the work, in stead of loading all data from different
(large) tables to the client.

The view can (must) then be defined as an entity within Uniface, and
can be painted as a normal entity. The view-mechanism is a major
performance feature when you use Uniface on a large complex database.

We use the Uniface / Allbase combination on 14 sites, each having
their own HP3000.

I am sure there are more useful examples, like stored procedures.

FHarasleben <[log in to unmask]> wrote:

>Hi,
>
>trying to get the pieces for a new application together (we are an
>austrian based Credit Insurance Company) we talked about ALLBASE as
>second DBMS system.
>
>Our current application is based on TurboImage and Powerhouse. The new
>application should be developed in the ClientServer environment using
>UNIFACE.
>
>Now, what could ALLBASE offer, what TurboImage can4t.
>
>Are there users out there who already use UNIFACE in HP3000 environments.
>
>I would appreciate every contact, comment etc., either to the newsgroup,
>to the LISTSERVER or to my mailbox ([log in to unmask]) directly.
>
>TIA,
>
>Friedrich

Mario Huizinga
Inspectie Gezondeidsbescherming
The Netherlands
email: [log in to unmask]