HyperDex - Instructions for using files ======================================= HyperDex Copyright (c) 1991,1992,1993 Text Technology All Rights Reserved HyperShell and HyperDex are trademarks of Text Technology. HyperDex is now SHAREWARE. Please read the READ.ME file in the main HyperShell disk for details of what this means. THIS SOFTWARE IS PROVIDED 'AS IS' AND TEXT TECHNOLOGY DISCLAIMS ALL WARRANTIES RELATING TO THESE SOFTWARE PRODUCTS, WHETHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, AND ALL SUCH WARRANTIES ARE EXPRESSLY AND SPECIFICALLY DISCLAIMED. NEITHER TEXT TECHNOLOGY NOR ITS AGENTS SHALL BE LIABLE FOR ANY INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE SUCH SOFTWARE EVEN IF TEXT TECHNOLOGY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR CLAIMS. IN NO EVENT SHALL TEXT TECHNOLOGY'S LIABILITY FOR ANY DAMAGES EVER EXCEED THE PRICE PAID FOR THE LICENCE TO USE THE SOFTWARE, REGARDLESS OF THE FORM OF CLAIM. THE PERSON USING THE SOFTWARE BEARS ALL RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE. You may give copies of applications developed, along with HDR.EXE, provided no fee is charged, and an acknowledgement is given indicating that HyperDex was used, and giving the name and address of Text Technology. Development licence holders may distribute HDR.EXE, HDB.EXE and HDX.EXE with their applications, subject to the terms stated in the printed documentation. Part or all of CARS.HYP, and generated hyperfiles from DBSKEL.HSL, may be used in your own hyperfiles. The DBM.HYP hyperfile MUST NOT be copied, in whole or in part, in any application given or sold. Techniques used therein may be utilised in your own applications, however. Installation ------------ *********** DO NOT RUN ON THE DISTRIBUTION DISK **************** ***** COPY TO BACKUP BEFORE USE **** RETAIN THIS AND USE COPY ** Simply copy the programs to a directory on the hard disk, or to another floppy disk. You need one of the .EXE files, along with the target .DBF/.NDX files. to run HyperDex. HDX.EXE also requires HS_IDE.HYP for development of hyperfiles. Programs -------- hdb.exe General HyperDex program hdr.exe Readonly version - cannot change database hdx.exe Development program (Requires HS_IDE.HYP or similar) hdg.exe Version of hdb supporting graphics like HG.EXE Database management ------------------- This can be used for setting up databases and indexes, for restructuring databases, and for browsing and modifying databases. The hyperfile generation step requires HC.EXE from the HyperShell V4.5 release, as well as dbskel.hsl. Instructions are given in the help menu. dbm.hyp General Database management hyperfile dbskel.hsl Skeleton hyperfile used by dbm.hyp To run, type:- hdb dbm Cars example ------------ This is an example of a multi-database application. The cars database and the insurance group database are 'joined' to display associated data. The cars database can be modified, and records can be added to it. cardem.hyp Control hyperfile cars.dbf Cars database cartype.ndx Car type index insgrp.dbf Insurance group database insgrp.ndx Insurance group index To run, type:- hdb cardem ---------------------------------------------------------------------- Additional information ---------------------- Before adding memo data to a record, the record must be written - The >A action on its own does not appear to do this. When adding a new record, the action >A can be followed immediately by >W to enable memo information to be added. ---------------------------------------------------------------------- Version History --------------- Development version - June 1991 Initial version for internal use on major conversion project V1.0 - March 1992 First public version V1.0[b] - June 1992 Fixed bugs 1. >n action did not work Parameters not processed 2. Logical fields could only be set to true with a positive integer Can now use string starting T,t,Y or y to indicate true 3. >x action when index not selected causes hang This is now prevented 4. Miscellaneous problems with DBM.HYP sorted out Memo fields Writing new record Display problems 5. DBSKEL.HSL modified to support memo fields 6. Editing a memo field when one does not exist is now possible. Using >m on an existing memo field causes the original data to be lost. It is therefore recommended that >M is always used unless the data is to be overwritten. Version 2.0 for HyperShell V5 release 1. Support for graphics and other resources held in memo fields 2. Other extensions as per V5 of HyperShell (see main documentation) =============================================================== See HyperShell documentation for full details of agents etc. Text Technology 66 Kennedy Avenue Macclesfield Cheshire SK10 3DE England () 0625 431357 email: ntaylor@cix.compulink.co.uk