Dec 062017
Utility for Clipper programmers that will extract field information to a file or memory variables. | |||
---|---|---|---|
File Name | File Size | Zip Size | Zip Type |
DBASE.DAT | 341 | 192 | deflated |
DBASE.DBF | 274 | 110 | deflated |
DBASE.DBT | 512 | 8 | deflated |
DBASE.GET | 230 | 84 | deflated |
DBASE.PRI | 88 | 50 | deflated |
DBASE.PUB | 83 | 50 | deflated |
DBASE.REP | 173 | 77 | deflated |
DBASE.SAY | 143 | 63 | deflated |
DBASE.SPA | 133 | 86 | deflated |
DBASE.STO | 153 | 73 | deflated |
DTEXT.DOC | 9556 | 2751 | deflated |
DTEXT.EXE | 41992 | 21905 | deflated |
Download File DTB104F.ZIP Here
Contents of the DTEXT.DOC file
sytems development, inc.
p.o. box 3377
honolulu, hawaii 96801
(808) 622-5878
dtext.exe (c) copyright 1989, 1990 systems development, inc.
dtext.doc (c) copyright 1989, 1990 systems development, inc.
dtext.exe v1.4e release may 1990
dtext.exe v1.4f release may 1990
dtext.doc v1.1 release may 1990
dtext.doc v1.2 release may 1990
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 1
Table of Contents
-----------------
Introduction ................................. 2
Licensing .................................... 2
Using Dtext .................................. 3
File Formats ................................. 4
Thanks ....................................... 8
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 2
Introduction
------------
dtext.exe is a utility program for the clipper programmer. Dbase
programmers can also use dtext.
dtext extracts the field information from the database and outputs the
the results in one of these output files:
dbase.REP replace field with memory variables
dbase.SPA initialized memory variables
dbase.PRI declares private memory variables
dbase.PUB declares public memory variables
dbase.STO stores memory variables with field
dbase.SAY says memory variables
dbase.GET gets memory variables
dbase.DAT list data base structure
Licensing
---------
This program and the documentation is given out as SHAREWARE. The copyright
belongs to SYSTEMS DEVELOPMENT, INC. If you use the program you are
required to register with a $5.00 registration fee to systems development.
No guarantees and no warranties are given to the user of Dtext.exe program.
It's your sole responsiblity for any damages, if you are planning to work
with "loaded" database files ... use with CAUTION! Always work with backup
database files, if your database file contains any data.
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 3
Installing Dtext
----------------
1) Make sure your CONFIG.SYS file is set up with files=20 or more.
2) Copy Dtext.exe to drive and directory where PATH can find it.
Your all ready to go ...
Notations
---------
How to Use Dtext
----------------
From the DOS prompt type DTEXT
DTEXT without the database file will always return an errorcode. The
errorcode is used interally by the program, on error the help screen is
display. You'll get a full listing of the avaliable switches.
Usage: dtext {d:\}database {d:\}outputdrive {-|/}{switches}
-al all database text dump*
-re replace text dump [replace field with mvariable]
-st store text dump [store field to mvariable]
-sp space text dump [store space(#) [0] to mvariable]
-pr private text dump [private mvariable]
-pu public text dump [public mvariable]
-sa say text dump [@ row+*,col+# say mvariable]
-ge get text dump [@ row+*,col+# get mvariable picture "@!"]
-da database dump [field] [type] [length] [decimal]
-lo write long format
-sh write short format* *=default =reserved
C:\> DTEXT DATABASE
If no output drive is given then the current drive and directory is used as
the default.
If no switches are given then the -al and -sh switches are used as the
default.
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 4
File Formats.
Example file formats are given for the temp1.dbf data base file. All files
with the filename dbase.??? are related.
Dtext uses the input filename as the output filename with a new filename
extention to match the output.
dbase.REP (-re)
------------------
When you read the user input using GETs and memory_variables. You'll
want to place them into the database record with APPEND BLANK and
REPLACE field with memory_variable. Example:
store space(25) to mname
@ 2, 5 say "Enter Last Name:"
@ 3, 4 say "Enter First Name:"
@ 2, 22 get mlname picture "@!"
@ 3, 22 get mfname picture "@!"
read
append blank
replace lname with mlname
replace fname with mfname
Dtext reads the data ase header and the field infomation to produces a
ASCII text file containing the lines:
replace [fieldname1] with m[memory variable1]
replace [fieldname2] with m[memory variable2]
...
replace [fieldnameN] with m[memory variableN]
or
replace [fieldname1] with m[memory variable1],
[fieldname2] with m[memory variable2],
...
[fieldnameN] with m[memory variableN]
The first format is the long format, which I like becuase it's easier
for me to read. You can choose this format with the -lo switch.
Instead of, the short format, which is the default format. If no
format switch is given, Dtext will produce the short format using -sh
switch.
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 5
File Formats.
dbase.SPA (-sp)
---------------
Memory variables must be cleared and initialized for new data entry.
*.SPA file produces a file with the initialized memory variables.
Character fields:
store space(character field length) to mfieldname
ADDED ( v1.4f ) -lo switch will allow you to produce generic form of
store space().
store space( len( fieldname ) ) to mfielname
Numerical fields:
store 0 to mfieldname
Logical fields:
store .t. to mfieldname
Date fields:
store ctod(" / / ") to mfieldname
Memo fields:
store "memo" to mfieldname
dbase.SAY (-sa)
---------------
reserved for future product additions.
dbase.GET (-ge)
---------------
reserved for future product additions.
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 6
File Formats.
dbase.PRI (-pr)
-----------------
Memory variables are declared as private or public. This file contains
the declaration of private variable.
You have the choice of two formats, long or short.
The default format (-sh) is the Short format.
private mfieldname1,
mfieldname2,
...,
mfieldnameN
The long format (-lo) produces the following:
private mfieldname1
private mfieldname2
private ...
private mfieldnameN
dbase.PUB (-pu)
-----------------
Memory variables are declared as private or public. This file contains
the declaration of public variable.
You have the choice of two formats, long or short.
The default format (-sh) is the Short format.
public mfieldname1,
mfieldname2,
...,
mfieldnameN
The long format (-lo) produces the following:
public mfieldname1
public mfieldname2
public ...
Public mfieldnameN
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 7
File Formats.
dbase.STO (-st)
-----------------
This file contains the code to store the field data to the memory variables.
store fieldname1 to mfieldname1
store fieldname2 to mfieldname2
...
store fieldnameN to mfieldnameN
dbase.DAT (-da)
-----------------
This file produces a listing of the field information.
You have the choice of two formats, long or short.
The default format (-sh) is the Short format.
fielname1 type length decimal
fielname2 type length decimal
...
fielnameN type length decimal
The long format adds header and data base information.
Data Base File:
Data Base Type:
Last Updated:
Number of Records:
Number of Fields:
Bytes per Record:
Header Size:
dtext.doc (c) copyright 1989, 1990 systems development, inc. Page 8
Thank you for your support! If you have ANY comments or bugs you may
write to:
systems development, inc.
p.o. box 3377
honolulu, hawaii 96801
(808) 622-5878
Compuserve 72417,1505
Systems Development, Inc. BBS ( unavaliable at release time )
It's best to write or call, since I don't like Compuserve!
Systems Development, Inc. BBS
-----------------------------
Running PCBoard with FastComm 9696 v.32 with MNP-5 at 8-N-1 ( 2400, 9600 )
Hayes 9600V at 8-N-1 ( 2400, 9600 )
This board supports programmers, BASIC, C, PASCAL, ASSEMBLY and CLIPPER.
copyright 1989, 1990 (c) systems development, inc. All rights reserved.
December 6, 2017
Add comments