Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!pyramid!ncc!apss!nmm
From: nmm@apss.ab.ca (Neil McCulloch)
Newsgroups: comp.databases
Subject: Re: INGRES/Expert system interfaces
Summary: screen dumps in Empress
Message-ID: <626@apss.apss.ab.ca>
Date: 18 Nov 88 19:35:15 GMT
References: <696@afit-ab.arpa> <1087@cps3xx.UUCP> <519@bloom.UUCP>
Organization: Alberta Public Safety Services
Lines: 29

In article <519@bloom.UUCP>, bobd@bloom.UUCP (Bob Donaldson) writes:
> In article <1087@cps3xx.UUCP>, kuan@cpsvax.cps.msu.edu (Yih-pyng Kuan) writes:
> > A very simple problem.
> > We are using Rhodnius Empress Relational DB. Can anybody tell me if we
> > can print out forms of the application for documentation ?
> > Thanks in advance.
> 
> I assume you really DO mean the mbuilder_form table, and not ALL the mbuilder
> tables.  The latter can be had by using mbprint <application name>.  We have
> used a print screen function from a PC hooked up as a terminal to our Sun
> network (where Empress runs).  As far as I know, that's the option.

mbprint prints the application itself which is not what the original
poster wanted. 

In Empress 2.4, from mbuilder, screen dumps are controlled by
the MSSCPRINTSCREEN variable. This can be set in the db tablezero
file or from the shell. eg:
				set MSCCPRINTSCREEN="Pscreendump"

will assign the screendump function to ^P. SUccessive screendumps will
be concatenated.  mbuilder will ofcourse let you assign any function
key you like to dump the screen to anywhere you like.

Alternatively, you can define a key in the termdb for screen dumping
which will only be active on those screens you choose.

My own question is: does MSSCFLUSHTYPEAHEAD to work? If so, what's the
secret.