Dec 112017
dBINDER intelligently binds your dBASE/FoxBASE program files. You give dBINDER the name of your top program file and it searches for all other program files used by the system. It then binds these files together to form | |||
---|---|---|---|
File Name | File Size | Zip Size | Zip Type |
DBINDER.DOC | 2498 | 1136 | deflated |
DBINDER.EXE | 10598 | 10269 | deflated |
Download File DBINDER.ZIP Here
Contents of the DBINDER.DOC file
DOC File for DBINDER.EXE
dBINDER 2.0 is a upgrade to dBINDER 1.0. This version adds the ability to
unbind procedure files.
dBINDER Binding Mode
dBINDER intelligently binds your dBASE/FoxBASE program files. You give dBINDER
the name of your top program file and it searches for all other program files
used by the system. It then binds these files together to form one procedure
file. The procedures are automatically labelled and a RETURN command is
appended to the end of the procedure.
dBINDER is not smart enough to pick up files that are referenced by macros.
For example: DO &FILE
dBINDER cannot trace through your source code to determine what filename is
stored the FILE variable.
The procedure file that dBINDER produces is named DBINDER.BND. dBINDER is
fully renamable. If you don't like the name I've given this program, simply
rename it to whatever you want. If you change the name to BIND.EXE then the
output file will become BIND.BND. The .BND extension is hard coded and cannot
be changed.
dBINDER Unbinding Mode
dBINDER will split procedure files into separate PRG files. This allows you
to pick apart procedure files more easily. Unbinding is fairly straightforward,
PRG file filenames are taken from procedure names and given the extension of
.UBD (UnBounD). Duplicate filenames may occur due to the 8 character limit on
filenames in DOS. This will happen when you have procedure names like
FUNCTION1 and FUNCTION2. These will both translate to FUNCTION.UBD so dBINDER
will name the second file DUP0000.UBD. All subsequent duplicate files will be
named DUP0001.UBD and so on and so forth. On the first line of the output files
will be a comment with the full name of the procedure. dBINDER also gives you
a warning to let you know when this happens. The warnings are written to
standard out (stdout) and may be redirected to another file.
USAGE
The syntax is: dBINDER filename (dBINDER will automatically determine whether to
bind or unbind the file)
dBINDER -u filename (to unbind the file)
dBINDER -b filename (to bind the file)
dBINDER ? (to display the help screen)
The parameters are not position sensitive (except for the ?). You can execute
dBINDER filename -u if you wish. The dashes are also interchangeable with
slashes (dBINDER /u filename). Executing dBINDER without any arguments will
display the help screen.
Samuel R. Blackburn, GEnie: S.BLACKBURN2
dBINDER 2.0 is a upgrade to dBINDER 1.0. This version adds the ability to
unbind procedure files.
dBINDER Binding Mode
dBINDER intelligently binds your dBASE/FoxBASE program files. You give dBINDER
the name of your top program file and it searches for all other program files
used by the system. It then binds these files together to form one procedure
file. The procedures are automatically labelled and a RETURN command is
appended to the end of the procedure.
dBINDER is not smart enough to pick up files that are referenced by macros.
For example: DO &FILE
dBINDER cannot trace through your source code to determine what filename is
stored the FILE variable.
The procedure file that dBINDER produces is named DBINDER.BND. dBINDER is
fully renamable. If you don't like the name I've given this program, simply
rename it to whatever you want. If you change the name to BIND.EXE then the
output file will become BIND.BND. The .BND extension is hard coded and cannot
be changed.
dBINDER Unbinding Mode
dBINDER will split procedure files into separate PRG files. This allows you
to pick apart procedure files more easily. Unbinding is fairly straightforward,
PRG file filenames are taken from procedure names and given the extension of
.UBD (UnBounD). Duplicate filenames may occur due to the 8 character limit on
filenames in DOS. This will happen when you have procedure names like
FUNCTION1 and FUNCTION2. These will both translate to FUNCTION.UBD so dBINDER
will name the second file DUP0000.UBD. All subsequent duplicate files will be
named DUP0001.UBD and so on and so forth. On the first line of the output files
will be a comment with the full name of the procedure. dBINDER also gives you
a warning to let you know when this happens. The warnings are written to
standard out (stdout) and may be redirected to another file.
USAGE
The syntax is: dBINDER filename (dBINDER will automatically determine whether to
bind or unbind the file)
dBINDER -u filename (to unbind the file)
dBINDER -b filename (to bind the file)
dBINDER ? (to display the help screen)
The parameters are not position sensitive (except for the ?). You can execute
dBINDER filename -u if you wish. The dashes are also interchangeable with
slashes (dBINDER /u filename). Executing dBINDER without any arguments will
display the help screen.
Samuel R. Blackburn, GEnie: S.BLACKBURN2
December 11, 2017
Add comments