Path: utzoo!attcan!uunet!cs.utexas.edu!usc!apple!oracle!news
From: tgreenla@oracle.uucp (Terry Greenlaw)
Newsgroups: comp.databases
Subject: Re: Oracle Forms & Wyse50/Vt100
Keywords: Oracle, Forms
Message-ID: <1990Feb21.001349.27092@oracle.com>
Date: 21 Feb 90 00:13:49 GMT
References: <361@cmsfl>
Reply-To: tgreenla@oracle.UUCP (Terry Greenlaw)
Organization: Oracle Corporation, Belmont, CA
Lines: 36

In article <361@cmsfl> nigel@cmsfl@labtam.oz (Nigel Harwood) writes:
>We are investigating Oracle Forms for use in an environment with
>NCR Towers, wyse50s and vt100s.
>
>As far as I can see the way Forms is set up you can only generate
>a form for one type of screen.
>
>This is going to be a problem for us if we intend using more than
>one type.
>
>Someone said the next release of Forms would handle this.
>
>Anyone know any more about this ?
>
>-- 
><<<<<<<<<<<<<<<<<<<<<<<  Nigel Harwood  >>>>>>>>>>>>>>>>>>>>>>>>>
><< Post:  Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >>
><< Phone: +61 3 829 6090      E-mail: nigel%cmsfl@labtam.oz.au >>
><<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

I'm assuming that you are talking about our SQL*Forms product. The 
forms themselves are NOT generated for a particular system. You specify
the terminal mapping at run time. You can even define terminal definitions
for off-the-wall CRT's through the (aptly named) CRT utility. The only time
that the CRT's type influences the form design is when you are working with
IBM mainframes in block mode. The forms will run on the IBM without making
any modifications, but because the transactions are running in blocks, you
lose the instant field validation that a character based terminal can provide.
Hope this helps.
tog


Terry O. Greenlaw             Sheathed within the Walkman, 
Staff Engineer                Wear a halo of distortion.
Oracle Corporation            Aural contraceptive,
tgreenla@oracle.oracle.com    Aborting pregnant conversation - Marillion