{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "DISK ID", "size": 44, "date": "1993-01-30", "time": "23:20" }, { "name": "INSTALL EXE", "size": 120313, "date": "1993-01-30", "time": "23:20" }, { "name": "INSTALL DAT", "size": 13484, "date": "1993-01-30", "time": "23:20" }, { "name": "4BIN LIF", "size": 137025, "date": "1993-01-30", "time": "23:20" }, { "name": "4OBJ LIF", "size": 55775, "date": "1993-01-30", "time": "23:20" }, { "name": "4LIB0 LIF", "size": 296028, "date": "1993-01-30", "time": "23:20" } ] } ], "volume": "CLIPDB 1OF3" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "DISK ID", "size": 44, "date": "1993-01-30", "time": "23:20" }, { "name": "4LIB1 LIF", "size": 296028, "date": "1993-01-30", "time": "23:20" }, { "name": "4LIB3 LIF", "size": 544922, "date": "1993-01-30", "time": "23:20" } ] } ], "volume": "CLIPDB 2OF3" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "DISK ID", "size": 44, "date": "1993-01-30", "time": "23:20" }, { "name": "INSTALL DAT", "size": 13487, "date": "1993-01-30", "time": "23:20" }, { "name": "4LIB2 LIF", "size": 83093, "date": "1993-01-30", "time": "23:20" }, { "name": "4INCL LIF", "size": 25386, "date": "1993-01-30", "time": "23:20" }, { "name": "4NATION LIF", "size": 66240, "date": "1993-01-30", "time": "23:20" }, { "name": "4SAMPLE LIF", "size": 58157, "date": "1993-01-30", "time": "23:20" }, { "name": "4NG LIF", "size": 58390, "date": "1993-01-30", "time": "23:20" }, { "name": "README KIT", "size": 18176, "date": "1993-01-30", "time": "23:20" } ] } ], "volume": "CLIPDB 3OF3" } }, "desc_file": "README.KIT", "desc_text": "========================================================================\r\n1 Welcome to Matt Whelan Compiler Kit - dBASE IV Edition\r\n\r\n Copyright (c) 1992 Nantucket Corporation. All rights reserved.\r\n\r\n This file contains the most up-to-date information about the\r\n product, including additional installation instructions and\r\n detailed distribution disk contents.\r\n\r\n\r\n\r\n\r\n========================================================================\r\n2 On-line Documentation\r\n\r\n The on-line documentation system consists of the Norton Instant\r\n Access Engine (NG.EXE) and several documentation databases that are\r\n listed below:\r\n\r\n IVKIT.NG The Guide to IV Kit\r\n (Compiler Kit reference)\r\n\r\n C5G01A.NG The Guide To Clipper\r\n (Clipper language and reference tables)\r\n\r\n C5G02A.NG Error Messages\r\n (Compiler, linker, runtime, RMAKE error messages)\r\n\r\n C5G03A.NG Extend System\r\n (Extend function reference documentation)\r\n\r\n C5G04A.NG Utilities\r\n (Utilities reference documentation)\r\n\r\n C5G05A.NG Release Notes\r\n (Change summaries and topical information)\r\n\r\n C5G06A.NG Sample Reference\r\n (Reference for sample programs)\r\n\r\n All of the documentation databases and the Instant Access Engine are\r\n installed in the default configuration into \\NG.\r\n\r\n\r\n========================================================================\r\n2 Performance Tips\r\n\r\n Due to the overhead required to handle dBASE IV extensions,\r\n performance for screens containing a large number of GETS may become\r\n slower than expected. Note that it is the GET creation, not the\r\n display which causes the reduction in performance, therefore\r\n anything you can do to avoid repetitive re-drawing will show a big\r\n improvement.\r\n\r\n 1. Use FORMAT files. With FMT files, GETs are only created the\r\n first time, and are kept for re-use on subsequent screens.\r\n\r\n 2. Save and re-use your GETs. We have added the following commands:\r\n\r\n SAVE GETS [ AS ]\r\n RESTORE GETS [ FROM ]\r\n RELEASE GETS [ FROM ] SHOW GETS\r\n\r\n Using these, a quick edit of your program should give instant\r\n benefits. Separate the screen-draw and GET code and only\r\n execute the GET code once, saving the GETs for re-use. Example:\r\n\r\n DO SETUP && first time\r\n\r\n DO WHILE dataentry\r\n\r\n RESTORE GETS FROM fred\r\n SHOW GETS\r\n READ\r\n ... etc\r\n ENDDO\r\n\r\n PROCEDURE SETUP\r\n\r\n DO SCRNDRAW && the ..SAY parts (should only need this once!)\r\n DO MYGETS && the ..GET parts\r\n SAVE GETS AS fred\r\n\r\n RETURN\r\n\r\n\r\n Popups\r\n\r\n One of the limitations of dBASE FIELD popups is they cannot\r\n accept an expression, and then load the whole database into memory.\r\n\r\n The IVKit popups do not need to load the entire database, can use\r\n expressions, and will make use of an index for key searching when\r\n it is available. You can obtain significant speed improvements by\r\n making sure there is a usable index active when invoking the Popup.\r\n To use expressions the syntax is virtually identical to other\r\n popups:\r\n\r\n DEFINE POPUP PROMPT EXPRESSION \r\n\r\n\r\n========================================================================\r\n3 Compatibility\r\n\r\n We have gone to extreme lengths to make the Compiler Kit compatible\r\n and easy to use. Most of our large test applications compile on\r\n 'auto-pilot', and we expect yours to as well.\r\n\r\n If this is not the case please let us know, and we'll do our best to\r\n fix it as quickly as possible. One of the benefits of the dBase\r\n language is its flexibility, but that can also be a problem for\r\n people like us. There are so many ways of using each command, and\r\n combinations of commands, that even the developers of dBase have\r\n probably never fully understood all of the variations.\r\n\r\n As well as offering you an early update to the 1.5 version of the\r\n kit, we will be providing regular updates through on-line services\r\n such as CompuServe. There is already a message section and library\r\n devoted to the Kit on the Nantucket Forum (GO NANFORUM).\r\n\r\n\r\n dBase IV Version 1.5\r\n --------------------\r\n\r\n The 1.1 version of the Compiler Kit was developed to be compatible\r\n with dBase IV Version 1.1. The recent release of Version 1.5\r\n introduced a range of new features which will be fully supported in\r\n your Kit update in the near future.\r\n\r\n However, we have already implemented almost all of the programming-\r\n related features of 1.5, including more than 25 new commands and\r\n functions. The only exceptions we've noticed in testing are mouse\r\n support, SET KEY index 'filters', the REINDEX option of verbs like\r\n APPEND, disk swapping for the RUN() function, and the LEFT/RIGHT\r\n components of the @...SCROLL command.\r\n\r\n Transaction Processing\r\n ----------------------\r\n\r\n Another feature we've left incomplete pending the update is\r\n Transaction Processing. As you'll see if you look closely at our\r\n translation files, we have embedded Transaction support in the\r\n system. However, a last-minute change in the Transaction Log\r\n format in dBase itself meant we felt safer holding this component\r\n for the update.\r\n\r\n We only discovered the change in dBase version 1.5 a few weeks\r\n before shipping the Compiler Kit and did not want to introduce\r\n potentially costly bugs in such an important component by making\r\n last-minute changes.\r\n\r\n\r\n========================================================================\r\n4 Using the Compiler Kit within Windows 3.x:\r\n\r\n To use the Compiler Kit under Windows 3.x, first add the file\r\n COMPILEW.BAT as a new Program Item. An icon for the Compiler Kit\r\n is provided in the file KIT.ICO.\r\n\r\n When invoking COMPILEW.BAT from within Windows, you are given the\r\n option to specify parameters. Specify the path to the files, the\r\n file(s) you want to compile, and any command line options.\r\n\r\n NOTE: The COMPILEW.BAT file expects the first parameter to be\r\n the path to the file(s); this path MUST include a trailing\r\n backslash!. It will pass this to dPrep using the /I\r\n switch so dPrep can find the files to compile, and will also use\r\n the supplied path to tell the Compiler utilities where to start\r\n work.\r\n\r\n You may also want to modify the COMPILEW.BAT file to automatically\r\n run the resulting EXE after compilation. The batch file parameter\r\n %2 will contain the name of the main program, thus the\r\n modification to COMPILEW.BAT would be as follows:\r\n\r\n ...\r\n if errorlevel 1 goto errmake\r\n %2\r\n goto end\r\n ...\r\n\r\n\r\n If you always compile programs in the same directory, there is an\r\n alternative to using COMPILEW.BAT. You can add the COMPILE.BAT file\r\n as a new Program item, and modify the COMPILE.PIF file so that the\r\n start-up directory points to the appropriate directory. In this\r\n case you would not specify the path when invoking COMPILE.BAT, just\r\n the file(s) you wish to compile and any command line options.\r\n\r\n To modify COMPILE.BAT to automatically execute the resulting EXE,\r\n you would use the %1 parameter as follows:\r\n\r\n ...\r\n if errorlevel 1 goto errmake\r\n %1\r\n goto end\r\n ...\r\n\r\n========================================================================\r\n5 Installation Problems\r\n\r\n This section provides information on the installation procedure for\r\n the Compiler Kit. If you have problems installing the software,\r\n consult the following list of problems and solutions. If you\r\n experience an installation problem not listed here, please contact\r\n Nantucket Support at the Nantucket office serving your country.\r\n Telephone numbers appear in the Contacting Nantucket section of the\r\n Product and Services Guide.\r\n\r\n When contacting Nantucket Support, have ready information about your\r\n environment such as: machine make and model, DOS version, memory\r\n available during installation, and any memory-resident software you\r\n are using.\r\n\r\n\r\n5.1 Command-line Arguments\r\n\r\n The following table shows the command-line arguments for\r\n INSTALL.EXE.\r\n\r\n Table: INSTALL.EXE Command-line Arguments\r\n -------------------------------------------------------------------\r\n Argument Description\r\n -------------------------------------------------------------------\r\n /NOSWAP Do not swap to EMS or disk\r\n /BW Monochrome for color display (for Laptops)\r\n /MONO Force monochrome display\r\n -------------------------------------------------------------------\r\n\r\n\r\n5.2 Modifying Your Environment Variables\r\n\r\n Certain environment (SET command) variables should be set for the\r\n Compiler Kit. If you elected to modify the AUTOEXEC.BAT file\r\n during the installation process, your file should be up-to-date.\r\n Otherwise, the appropriate settings should be in a file called\r\n AUTOEXEC.CHG located in the \\CLIPPER5 directory. In either case,\r\n it is important that you modify your AUTOEXEC.BAT file to\r\n incorporate these additional settings so that the Compiler Kit\r\n will know where to find files. The required settings are as\r\n follows:\r\n\r\n 1. The PATH variable should include the directory where\r\n executable files reside (example: C:\\CLIPPER5\\BIN).\r\n\r\n 2. The LIB variable should include the directory where library\r\n files reside (example: C:\\CLIPPER5\\LIB).\r\n\r\n 3. The INCLUDE variable should include the directory where\r\n include files reside (example: C:\\CLIPPER5\\INCLUDE).\r\n\r\n 4. The PLL variable should include the directory where pre-linked\r\n library files reside (example: C:\\CLIPPER5\\PLL).\r\n\r\n For example:\r\n\r\n SET PATH=C:\\CLIPPER5\\BIN;%PATH%\r\n SET LIB=C:\\CLIPPER5\\LIB\r\n SET INCLUDE=C:\\CLIPPER5\\INCLUDE\r\n SET PLL=C:\\CLIPPER5\\INCLUDE\r\n\r\n You may also wish to set other environment variables. For more\r\n information, refer to the Getting Started Guide and Programming and\r\n Utilities Guide. For general information about the DOS environment\r\n and setting environment variables, refer to your DOS manual.\r\n\r\n\r\n\r\n========================================================================\r\n6 Distribution Disk Contents\r\n\r\n This section provides information regarding the contents of the\r\n Compiler Kit distribution disks. The files are described in general\r\n terms of their contents followed by several tables showing the\r\n various disk configurations.\r\n\r\n\r\n6.1 Disk Identifier Files\r\n\r\n Each disk in the Compiler Kit package contains a file named DISK.ID\r\n that is used by the install program to verify version and disk\r\n number.\r\n\r\n\r\n6.2 Install Files\r\n\r\n The install program (INSTALL.EXE) and the installation script\r\n (INSTALL.DAT) are located on Disk 1. Together, these two files\r\n allow you to install the Compiler Kit onto your hard disk.\r\n\r\n\r\n6.3 Archive Files\r\n\r\n The Compiler Kit distribution files are supplied in the form of\r\n archive files. Most of the archive files have a .LIF extension,\r\n but the file containing the main documentation database is split up\r\n into two files with .001 and .002 extensions. Each of the archive\r\n files is listed in the table below, followed by several tables\r\n showing the contents of each archive file.\r\n\r\n Table: Archive File Descriptions\r\n -------------------------------------------------------------------\r\n Archive Contents\r\n -------------------------------------------------------------------\r\n 4BIN.LIF DPREP program\r\n 4OBJ.LIF Compiler Kit object files and database driver\r\n 4LIB1.LIF Compiler Kit support libraries\r\n 4LIB2.LIF Compiler Kit support libraries\r\n 4INCL.LIF Compiler Kit header files\r\n 4NATION.LIF Nations Language support\r\n 4SAMPLE.LIF Compiler Kit sample application\r\n 4NG.LIF On-line documentation database\r\n -------------------------------------------------------------------\r\n\r\n\r\n Table: 4BIN.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n DPREP.EXE dBASE IV .prg pre-processor program\r\n DPREP.CFG Configuration file for DPREP.EXE\r\n DPREP.RSV Reserved word list\r\n COMPILE.BAT Compilation batch file\r\n COMPILE.PIF Program information file for COMPILE.BAT\r\n COMPILEW.BAT Compilation batch file for use with Windows 3.x\r\n COMPILEW.PIF Program information file for COMPILEW.BAT\r\n KIT.ICO Windows icon for Compiler Kit\r\n\r\n\r\n Table: 4LIB1.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n IVKIT.LIB Compiler Kit library\r\n IVTOOLS.LIB Compiler Kit library\r\n\r\n\r\n Table: 4LIB2.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n DB4DBF.LIB dBASE IV DBF driver\r\n DBFNTXN.LIB Special NTX driver for Compiler Kit\r\n DBASEIV.LNK .RTlink script for building pre-linked library\r\n\r\n\r\n Table: 4OBJ.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n DBFMDX.LIB dBASE IV MDX driver\r\n IVTOOLS.OBJ Compiler Kit support routines\r\n\r\n\r\n Table: 4INCL.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n D4STD.CH Header file for standard command set\r\n DPSTD.CH Translations for dBASE IV commands\r\n DPDEFS.CH Preprocessor directives\r\n\r\n\r\n -------------------------------------------------------------------\r\n Table: 4NATION.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n NATION.BAT Batch program to change selected language default\r\n CHOOSE.COM Batch utility\r\n NAT_USA.LIB US English Nations Library (US Collation sequences)\r\n NAT_UK.LIB UK English Nations Library (UK Collation sequences)\r\n NAT_FREN.LIB French Nations Library (French Collation sequences)\r\n NAT_DUTC.LIB Dutch Nations Library (Dutch Collation sequences)\r\n NAT_SPAN.LIB Spanish Nations Library (Spanish Collation sequences)\r\n\r\n\r\n Table: 4SAMPLE.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n DEMO.PRG Sample application - main program\r\n DEMOBAR.PRG Sample application - support file\r\n DEMOMDX.PRG Sample application - support file\r\n DEMOQRYP.PRG Sample application - support file\r\n DEMOSCR.PRG Sample application - support file\r\n DEMO.DBF Sample database\r\n DEMO.MDX Multiple index file\r\n DEMO.FMT Format file\r\n DEMOQBE.QBE Sample QBE file\r\n DEMORPT1.FRG Generated report\r\n DEMORPT2.FRG Generated report\r\n DEMOLBL1.LBG Generated label\r\n DEMOLBL2.LBG Generated label\r\n DEMO.APP Application definition file\r\n DEMOBAR.BAR Menu definition file\r\n DEMOEXIT.POP Menu definition file\r\n DEMOMNTN.POP Menu definition file\r\n DEMOQRYM.POP Menu definition file\r\n DEMOREC.POP Menu definition file\r\n DEMOFILE.FIL File list definition\r\n DEMORPT1.FRM Report definition file\r\n DEMORPT2.FRM Report definition file\r\n DEMOLBL1.LBL Label definition file\r\n DEMOLBL2.LBL Label definition file\r\n DEMO.SCR Screen definition file\r\n\r\n\r\n Table: 4NG.LIF Archive File Contents\r\n -------------------------------------------------------------------\r\n File Contents\r\n -------------------------------------------------------------------\r\n IVKIT.NG Compiler Kit on-line documentation database\r\n NG.INI Setup file for Norton Instant Access Engine\r\n\r\n\r\n\r\n========================================================================\r\n7 Copyrights\r\n\r\n The installation program used to install the Compiler Kit,\r\n INSTALL, is based on licensed software provided by Knowledge\r\n Dynamics Corp, Highway Contract 4 Box 185-H, Canyon Lake, Texas\r\n 78133-3508 (USA), 1-512-964-3994. INSTALL is Copyright (c) 1987-\r\n 1991 by Knowledge Dynamics Corp which reserves all copyright\r\n protection worldwide. INSTALL is provided to you for the\r\n exclusive purpose use of installing the Compiler Kit. Nantucket\r\n has made modifications to the software as provided by Knowledge\r\n Dynamics Corp, and thus the performance and behavior of the\r\n INSTALL program shipped with the Compiler Kit may not represent\r\n the performance and behavior of INSTALL as shipped by Knowledge\r\n Dynamics Corp. Nantucket is exclusively responsible for the\r\n support of the Compiler Kit, including support during the\r\n installation phase. In no event will Knowledge Dynamics Corp be\r\n able to provide any technical support for the Compiler Kit.\r\n\r\n\r\n\r\n\r\n * * *\r\n\r\n\r\n\u001a" }