Q. My make script stops part way and doesn't complete.

A. If any action in the make fails, PBMake intentionally stops.

   If you are compiling a module, and your compiler ends with an
   errorlevel higher than 0 when it quits, the make process stops.

   Compilers usually exit with an errorlevel of 0 if everything went OK.

   If you want Clipper to exit with an errorlevel when something goes
   wrong, you must add /ES2 to the FLAG= directive.
   (Clipper 5.0 or higher)

A. There are 5 directives which will allow you to run an executable
   file: SUCCESS=, FAILURE=, NONEED=, PRECOMPILECMD= and PRELINKCMD=.
   If you use one of these to run a batch file, and you forget to use
   the dos CALL command which allows nested batch files, MAKE.BAT will
   lose scope and stop running.

   Solution:
   Check your link script for any of the above directives, and check to
   see if they are calling a batch file. If so, place the CALL directive
   in the directive before the batch file name.

   SUCCESS= GOODRUN.BAT

   Should be:

   SUCCESS= CALL GOODRUN.BAT