╩╩FoxBinder will take a folder of FoxBase program files and create one large "Procedure" file out of them. It will use all files of type 'F+PR', so it will include all of your screen format files, but it is smart enough to ignore files that end with ".bak". It won't recursively go through folders inside the folder you select.
╩╩For more information about procedure files, refer to pages 6-12 and 6-31 in the new FoxBase User's Guide.
Ñ How to print these instructions
╩╩If you open this Application as a document in Microsoft Word (or any program or desk accessory capable of opening arbitrary documents) it will appear to be just these instructions. They can then be formatted and printed in whatever way you wish. In MS-Word, hold down the shift key while you select 'Open╔' from the 'File' menu. In McSink, hold down the Option key. (Don't try to save text into this program, though, or you'll break it!) Alternatively, you can change the Type of this file to 'TEXT' and open it with any word processor (but remember to change it back, or the program won't work).
Ñ How to use FoxBinder
╩╩FoxBinder will present you with a standard file dialog box, and ask you which file to start with. Select your main program file (the one which should be run first). Two options, which are checked by default, are available.
╩╩╩╩(1) Strip out ".prg" in Procedure names:
With this option checked, FoxBinder generates lines like "Procedure procedurename" at the start of each module. If you want it to write "Procedure procedurename.PRG" you should uncheck this.
╩╩╩╩(2) Generate "Set Procedure" Line:
With this option checked, FoxBinder generates "Set Procedure To procedurefile.PRG" at the very start of your procedure file. This means you don't have to add that yourself before you bind all your modules with FoxBinder. If for some reason you don't want this, uncheck this option.
╩╩After you choose your main program file, FoxBinder asks for the name of the procedure file it will create. It will use this name in the "Set Procedure" line it puts at the beginning of the procedure file (if you leave the appropriate option checked).
Ñ Error Handling
╩╩Generally, if there is a Mac error, it will be reported as a number. FoxBinder will then try to close any open files and quit to the Finder. If one of your modules is ridiculously large (about 150K), FoxBinder may crash or behave badly. There is no limit on the size of the final procedure file, however.
╩╩If you get a "Fatal Error -9999" that means that you ran out of disk space or your disk has some other problem. This is NOT a bug in FoxBinder .
* The body of the first subroutine module goes here
* etc.
----------
╩╩Remember, the options in the Standard File dialog will govern the exact appearance of this file.
Ñ Revision History
╩╩Version 1.1 - Fixed minor bug which prevented saving procedure files in a folder different from the source files'. Added scrolling help window and better window placement. Compiled with LSP 2.0.
Ñ Credits
╩╩Without Think's Lightspeed Pascal, this would have been written in assembler. It might have been available by 1990.
╩╩Without Fox Software's FoxBase+/Mac, I might still be using Omnis or 4D. I might be insane by 1990...
