Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!snorkelwacker!tut.cis.ohio-state.edu!ucbvax!agate!violet.berkeley.edu!steve
From: steve@violet.berkeley.edu (Steve Goldfield)
Newsgroups: comp.databases
Subject: Re: DATAFLEX
Keywords: RDBMS, Dataflex
Message-ID: <1990Feb9.215048.10663@agate.berkeley.edu>
Date: 9 Feb 90 21:50:48 GMT
References: <16703@boulder.Colorado.EDU> <6023@ct.sei.cmu.edu>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 19

In article <6023@ct.sei.cmu.edu> tac@sei.cmu.edu (Timothy Coddington) writes:
#>In article <16703@boulder.Colorado.EDU> deac@tigger.colorado.edu (Deac Lancaster) writes:
#>Dataflex has several very unique features.
#>First, creating input screens is very easy.  Simply, create a file
#>containing a "picture" of how you want your screen to look.  That is, using
#>ascii and block graphic characters format how you want it to look.  For
#>entry field, which are eventually highlighted during data entry, you use
#>some designated character (such as underscore).  A period in an entry field
#>means it will be an integer or float, depending on where you put it.  When
#>your done you feed it to a utility that generates the program source AND
#>database definition/structure for entering and modifying records defined by
>your entry screen.  However, most of the time there is more to the
>processing, but this is a very helpful first step.

That feature is hardly unique. When I bought CP/M dBASE II in
1983, it came with a utility called ZIP, which did essentially
the same thing.

Steve Goldfield