Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : DB3TOOLS.ZIP
Filename : CSAVEIT.DOC

Output of file : CSAVEIT.DOC contained in archive : DB3TOOLS.ZIP

SAVEIT dBASE III(1) Screen Save Call Routine
© 1986, Kenneth E. Wilson, Digital Equipment Corporation

This program is provided to the DECdomain with the condition that it
not be sold or included in any application which is sold. This program
is not warranted or guarranteed nor is it supported by its author. Any
problems found in this application should be logged in the dBASE notesfile.

This routine when loaded will save the Rainbow video screen to a specified
disk file. If the file cannot be created an error message will appear on the
screen and the routine will exit normally. Nothing will be written to the
screen unless the above error occurs. This routine is intended ONLY for
the following system configuration: RAINBOW 100A/B, dBASE III V1.1 on
MS-DOS(3) V2.11 or later.

To enable use of SAVEIT issue the following dBASE III command:

The call is structured as follows:

^ ^
|- Function |- Standard valid MS-DOS filespec

The screen that is saved with this routine is in the format of the screen
image file saved by the program DO-IT and SWITCH-IT/DESK(2). The file created
CANNOT be typed to the screen with the MS-DOS screen TYPE command.

See the PAINTIT and PRINTIT routines also available from this author.

This routine may work on dBASE III V1.0, but specific loading and calling
syntax is different and as I understand V1.0 only one routine can be loaded
at any one time.

(1) dBASE III is a trademark of Ashton-Tate
(2) SWITCH-IT/DESK is a trademark of VuSoft
(3) MS is a trademark of MicroSoft

  3 Responses to “Category : Dbase (Clipper, FoxBase, etc) Languages Source Code
Archive   : DB3TOOLS.ZIP
Filename : CSAVEIT.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: