home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power-Programmierung
/
CD1.mdf
/
assemblr
/
mslang
/
dbhex
/
dbhex.doc
< prev
next >
Wrap
Text File
|
1993-04-03
|
2KB
|
71 lines
Type
DBHEX < .dbf file name >
where < .dbf file name > is the name of a database file
and press <ENTER>.
Entering the .DBF extension is optional.
For example, each of the following lines would be valid:
DBHEX CUSTOMER
DBHEX CUSTOMER.DBF
DBHEX F:\PAYABLE\CUSTOMER.DBF
DBHEX F:\PAYABLE\CUSTOMER
DBHEX \PAYABLE\CUSTOMER
DBHEX is designed with the following type of folk in mind:
Programmers needing another external source to help confirm that
their routines are accessing .DBF file bytes at the correct
locations. There are plenty of other utilties for this purpose,
but many of them are part of larger programs and therefore may
not fit on one's favorite utility diskette.
Beginning assembly language programmers, who just want some code
to look at and play with, for fun or perhaps to decide for sure
whether assembly language is what they are looking for.
Programmers who are considering purchasing the Spontaneous
Assembly Library by BaseTwo Development, and would like to see
a non-trivial sample of the library's capabilities. However,
note that DBHEX references a fraction of the Spontaneous
Assembly modules, and that it should not be considered a
complete demonstration of the Spontaneous Assembly library.
DBHEX displays the contents of a dbase (.dbf) file in
hexadecimal format, separating clearly the header information
from field values. Along the way, it displays record numbers in
hex/decimal format, and the offset from the current 64K block
showing what location in the dbase file the displayed bytes are
being taken from. It also shows, to the right of the
hexadecimal characters, how these characters appear in ascii
format. If a hexadecimal character happens to be less than 20
hex (32 dec), it's ascii interpretation on the right is a
period.
It is assumed that the file specified is a valid .DBF file.
Many of the routines are dependent, for their correctness, on the
current location of the file pointer. For example,
GET_AND_DISP_HEADER doesn't work correctly unless the pointer is
at the beginning of the file.
Also note that much of the time, the file handle is required to
be in BL.
DBHEX was compiled in MASM 6.1. I believe it is TASM
compatible, as well.