BUILDRTM with PROISAM(D) Must Have OBJ and LIB in Export List (63268)

SUMMARY

To build ISAM support into a custom run-time module (instead of using ISAM from the separate TSR program), you must specify in BUILDRTM's Export List file both the object (.OBJ) and library (.LIB) forms of your chosen ISAM library (PROISAM or PROISAMD). If either the object or library form is left out of the Export List file, LINK.EXE flags numerous occurrences of L2025 ("Symbol defined more than once") and L2029 ("Unresolved external").

MORE INFORMATION

The following Export List file (arbitrarily named ISAM.EXP) shows the files that need to be specified to put PROISAMD into a custom run-time module:

# ISAM.EXP
#OBJECTS
PROISAMD.OBJ
# (specify additional OBJs here)
#LIBRARIES
PROISAMD.LIB

You must also specify an #EXPORTS list, which is a list of all the routines that you wish your program to access. For PROISAM, this would include routines such as INSERT, SEEKGT, CREATEINDEX, and so forth.

The command line to build the custom run-time module specified by the above Export List file is as follows:

   BUILDRTM /LR ISAMRUN ISAM.EXP

This BUILDRTM command outputs three files: IMPORT.OBJ and ISAMRUN.LIB (used to resolve LINK references to your custom run-time module) and ISAMRUN.EXE (your custom run-time module).

To LINK the above run-time module to a Basic program, use the following LINK command:

   LINK IMPORT.OBJ+yourfile.OBJ,yourfile.EXE,,ISAMRUN.LIB;

For more information about using BUILDRTM.EXE, see chapter 21, "Building Custom Run-Time Modules," in the "Microsoft Basic 7.0: Programmer's Guide" for 7.0 and 7.1.