advr.hlp (Topic list)
$INCLUDE Metacommand Details
  Summary  Details  Example                Contents  Index  Back
──────────────────────────────────────────────────────────────────────────────
 {REM | '} $INCLUDE: 'filespec'
 
 Usage Notes
   ■ Include files are often used to group $FORM metacommands, declarations,
     and constants. It is easier to maintain a single include file than to
     update multiple Declaration sections in a project. For example:
 
                             ┌───FORMS.BI──┐
                             │             │
             ┌───────────────│'$FORM Form1 │───────────────┐
             │               │'$FORM Form2 │               │
             │               │'$FORM Form3 │               │
             │               └─────────────┘               │
             │                      │                      │
             ▼                      ▼                      ▼
  ┌──────FORM1.FRM──────┐┌──────FORM2.FRM──────┐┌──────FORM3.FRM──────┐
  │                     ││                     ││                     │
  │'$INCLUDE 'FORMS.BI' ││'$INCLUDE 'FORMS.BI' ││'$INCLUDE 'FORMS.BI' │
  └─────────────────────┘└─────────────────────┘└─────────────────────┘
     See: Entering Declarations in Code
 
   ■ Include files created from the programming environment must be in text
     (not binary) format.
 
   ■ When adding an include file to your project, be sure to select the
     Include File [*.BI] option in the Add File dialog box.
 
   ■ To view include-file text, choose Included File from the View menu.
 
   ■ When you are running a program from the Visual Basic programming
     environment (VBDOS.EXE), include files must not contain SUB or
     FUNCTION statements.
 
   ■ When you are compiling a program using the Visual Basic Compiler
     (BC.EXE), include files can contain SUB or FUNCTION statements.
     See: BC Command-Line Options  VBDOS Command-Line Options