Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!mtxinu!sybase!calvin!ben
From: ben@calvin.sybase.com (ben ullrich)
Newsgroups: comp.databases
Subject: Re: Ingres vs Sybase
Message-ID: <4320@sybase.sybase.com>
Date: 19 May 89 17:22:08 GMT
References: <4306@elecvax.eecs.unsw.oz> <587@kylie.oz> <13656@ncoast.ORG>
Sender: news@sybase.sybase.com
Organization: sybase, inc., emeryville, ca
Lines: 29

In article <13656@ncoast.ORG> allbery@ncoast.UUCP (Brandon S. Allbery) writes:
>
>Oh -- on a slightly different tack, I was amused to note that there are
>*three* front-ends available for Oracle aside from Oracle's own:
>Accell/SQL, For-Ten (who?) and Progress (well, it's "in development").
>Quite a damning statement about SQL*Forms, if you ask me....  (There were
>four available for Sybase, but that's because Sybase's native forms package
>is bitmapped; all of these were character-oriented.)

Just a minor clarification:  Sybase's ``native forms package'' is terminal
independent:  the low-level routines worry about what terminal you're on; 
most any front-end application you might build with our forms packages
will run on both types of terminals with no modifications as long as
both terminals are supported.  The front ends run principally on *character*
terminals, and on bit-mapped workstation terminals if such an interface
is generally available with the machine.  Thus, Sybase supports
character-based front ends on, for example, Pyramid, with no bitmapped
terminal support, because Pyramid doesn't make bitmapped terminals for
its computers.  Similarly, Sun bitmaps and VAX Station bitmaps are
supported, since these are often standard equipment on a Sun or VAX
Station.


..ben
----
ben ullrich	       consider my words disclaimed,if you consider them at all
sybase, inc., emeryville, ca
+1 (415) 596 - 3500		     "skinheads are pinheads!" -- greg sullivan
ben@sybase.com			       {pyramid,pacbell,sun,lll-tis}!sybase!ben