%white,blue
╒═══════════════════════════════════════════════════════════════════════════╕
│                    QuikHelp Beta - Version 1.0                            │
│                         *** by DataBex ***                                │
│                                                                           │
│  Now Available - Version 1.1 ! (Started Shipping September 15, 1988)      │
│                                                                           │
│  o  450% FASTER Topical Indexing.                                         │
│  o  Updates to *ALL* Registered Users of Beta 1.0                         │
│  o  Registration is *FREE*                                                │
│  o  To Register: Send Name and Address to:                                │
│                              DataBex                                      │
│                   "QuikHelp - Beta Registration"                          │
│                      6065 Mission Gorge Road                              │
│                             Suite #414                                    │
│                        San Diego, CA 92120                                │
│  o  Or E-mail Name and Address on:                                        │
│                    -  MCI mail   - 650-318-9786                           │
│                    -  CompuServe - 72271,2152                             │
│                    -  The Source - AAN838                                 │
╘═══════════════════════════════════════════════════════════════════════════╛
                       QuikHelp Testing Program
                    Version 1.00 - Beta Shareware
@Main Menu 1
%aqua,magenta
* Program Name: quikhelp.hlp *
* (c) 1988 by DataBex *
**************************************************************************
* Created: 6/16/1988 at 11:29                                            *
* main = Version 1.00 - Shareware Distribution  .OBJ Module only.        *
* Revision:  Last Revised: 6/16/1988 at 11:55                            *
* Called From:                                                           *
*************************** ALL RIGHTS RESERVED **************************
  ╒═════════ Main Menu 1 ════════╕     
  │                              │     
  │                              │     
> │ [ Main Menu 2              ] │     
> │   QuikHelp Features          │       ╒═════════════════════╕
> │   Introduction to QuikHelp   │       │ * Q U I K H E L P * │
> │   QuikHelp specifications    │       ├─────────────────────┤
> │   Keyboard controls          │       │   Copyright 1988    │
> │   Menus                      │       │        by           │
> │   QuikHelp Screens           │       │      DataBex        │
> │   QuikHelp Formatting Hooks  │       │ All Rights Reserved │
> │   New Topic Hook             │       ╘═════════════════════╛   
> │   Screen Feed Hook           │         6065 Mission Gorge Road
> │   Menu Line Hook             │         Suite #414 
> │   Menu Delimiters            │         San Diego, CA 92120
> │   Comment Hook               │ 
> │   Color Selection Hook       │ Royalty-free On-line Reference System
  │                              │ for Clipper Applications Developers. 
  │                              │     
  ╘══════════════════════════════╛ 
@Main Menu 2
%red,white

  ╒═════════ Main Menu 2 ════════╕                                      
  │                              │  ╔════════════════════════════════╗  
> │ [Main Menu 1              ]  │  ║                                ║  
> │  QuikHelp BOF Behavior       │  ║                                ║  
> │  Interfacing with Clipper    │  ║       Q U I K H E L P          ║  
> │  Calling from DOS            │  ║                                ║  
> │  Debugging                   │  ║  QuikHelp can be incorporated  ║  
> │  Editors                     │  ║  in your Clipper programs.     ║  
> │  Help File Structure         │  ║     ** Royalty FREE **         ║  
> │  QHindex                     │  ║                                ║  
> │  QuikHelp Screen Structure   │  ║                                ║  
> │  Search Topic                │  ║  *NEWS FLASH/NEWS FLASH/NEWS FL║  
> │  Example of Use              │  ║  QuikHelp - Version 1.1        ║  
> │  Error Messages              │  ║  Started Shipping 09/15/88     ║  
> │  Versions 1.5/2.0 !!         │  ║  - 450% FASTER topical indexing║  
> │  Release 2.0                 │  ║  - Updates available to ALL    ║  
> │  The Wish List               │  ║    *Registered* users of Beta  ║  
> │  Free Support Policy         │  ║    version 1.0.                ║  
  ╘══════════════════════════════╛  ║  - *FREE* Registration         ║  
                                    ╚════════════════════════════════╝
@QuikHelp Features
%black,aqua



   ╔═════════════════════════════════════════════╦═════════════════════╗
   ║  QuikHelp Features                          ║  Limits             ║
   ╠═════════════════════════════════════════════╬═════════════════════╣
   ║  maximum key length                         ║  127                ║
   ║  maximum topics per help file               ║  1000               ║
   ║  maximum number of screens per help file    ║  unlimited          ║
   ║  maximum number of menus per help file      ║  unlimited          ║
   ║  maximum number of colors used              ║  unlimited          ║
   ║  maximum help file size                     ║  unlimited          ║
   ║  maximum menu selections per screen         ║  22                 ║
   ║  storage type                               ║  ASCII text file    ║
   ╚═════════════════════════════════════════════╩═════════════════════╝



    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Introduction to QuikHelp
%white,black

 Quikhelp has been designed for the Clipper Developer.  The design stems from
 the need to put full-system documentation on-line in an appealing and
 professional fashion, AND at the same time do so with a minimum amount of
 intervention from the Developer.

 Consequently, Quikhelp provides an easy-to-use set of "hooks" which allow
 the Developer to accomplish just that.  The control of text, format, menus,
 and color are all done through these "hooks".  All of these can be
 controlled with the developer's text editor.

 Quikhelp can be used on virtually any text file with a maximum character
per line count of 78, (more than adequate for most professionally produced
documentation.

        

    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@QuikHelp specifications
                              QuikHelp
   ╔═════════════════════════════════════════════════════════════════════╗
   ║                                                                     ║
   ║  Full-system documentation, On-line instantly                       ║
   ║  Topical reference search capability                                ║
   ║  Context-sensitive help                                             ║
   ║  Expandable, what-you-see-is-what-you-get style                     ║
   ║  ASCII file storage for all text & menus                            ║
   ║  Maximum lines per screen: 22                                       ║
   ║  Unlimited amount of menus                                          ║
   ║  Unlimited screens                                                  ║
   ║  Screens & Menus user-defined as part of the text                   ║
   ║  User definable help screens & menus                                ║
   ║  Dos, Dbase, Clipper, & FoxBase compatible                          ║
   ║  No recompiling after textual changes                               ║
   ║  No knowledge of dBASE or other programming language required       ║
   ║  Softcoding techniques through "hooks"                              ║
   ║                                                                     ║
   ╚═════════════════════════════════════════════════════════════════════╝
@Keyboard controls
%blue,white

 ┌───────────────┬──────────────────────────┐
 │  Key          │   Action                 │
 ├───────────────┼──────────────────────────┤
 │               │                          │             ┌─────────────────┐
>│  ESC..........│   exit QuikHelp          │             │  [Main Menu 1]  │
>│               │                          │             │   Main Menu 2   │
 │  ARROW KEYS...│   menu bar control       │             └─────────────────┘
 │               │                          │
 │  PgUp.........│   previous page          │
 │  PgDn.........│   next page              │
 │               │                          │
 │  ENTER........│   make a selection       │
 └───────────────┴──────────────────────────┘

^

 NOTE:

 If you see the "press a key to continue ..." message, pressing any
 key will show the next help screen.  Pressing the "PgDn" key produces the
 same effect.


@Menus
%white,blue

 Quikhelp menus are defined as an integral part of any screen.  Menus allow
 the user to select the topic desired.  The ">" hook (placed on the first
 COLUMN of text) designates a menu item.  The actual menu selection of text
 can be delimited with "[ ]" hooks.  These delimited hooks control the width
 of the menu item to be selected.  Each screen may contain ONE MENU of with a
 maximum of 22 menu items.



                      ┌──────── This is an example of QuikHelp menu
                      │
                      
                      ┌─────────────────┐
>                     │  [Main Menu 1]  │
>                     │   Main Menu 2   │
                      └─────────────────┘
^

 Each menu item should be a topical reference as Quikhelp will attempt to
 locate that topic when that menu item is selected.

 Notice how the "[ ]" hook delimiters are only placed on the first line of
 the menu.  The width of these hooks defines the width of the widest menu
 item.


  eg:

    ╔═════════════════════════════════════════════════════════════════╗
    ║                      Employee Maintenance                       ║
    ║                                                                 ║
    ║        Please select a help topic from the selection below:     ║
    ║                                                                 ║
>   ║>                         [[Input        ]]                      ║
>   ║>                           Review/Update                        ║
>   ║                            Deletion                             ║
>   ║                            Utility                              ║
    ╚═════════════════════════════════════════════════════════════════╝
^

 If the second menu item is selected ("Review/Update"), Quikhelp will search
 through the help file for a topical reference indicated in the help file by
 "@Review/Update".  If the reference if found, the section is displayed;
 otherwise, "No Match" is indicated and the help file is left at its current
 position.          

             ┌──────────────────────────────────┐
             │ Usage :   >     [ help topic ]   │
             └──────────────────────────────────┘


@QuikHelp Screens
%yellow,blue

 Since Quikhelp is a screen-oriented help/reference display facility, all
 screens receive equal treatment.  This means that menus and help text
 screens can be reviewed one at a time or referenced via a menu selection.

 Menus can be quickly created and maintained since they are just another
 part of the overall reference text.  While menus are not required, their
 inclusion provides a simple and reliable interface with the end user,
 providing the end user with the option of viewing only the information he
 selects.


    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@QuikHelp Formatting Codes 
%red,aqua

 Quikhelp provides you, the Developer, with six formatting codes or "hooks"
 to help control the presentation of the help/reference being displayed. 

 ALL "HOOKS" MUST BE PLACED ON COLUMN 0.

 EACH "HOOK" MUST BE ON ITS OWN LINE.

        ┌─────────┬────────────────────────────────┐
        │  HOOK   │    DEFINITION/ACTION           │
        ├─────────┼────────────────────────────────┤
        │         │                                │
        │    @    │    New selection topic         │
        │    %    │    color selection             │
        │    *    │    comment out line            │
        │    >    │    menu line                   │
        │    []   │    menu delimiters             │
        │    ^    │    new screen ( screen feed )  │
        └─────────┴────────────────────────────────┘
@New Topic Hook  
%magenta,black

                         New Topic Hook "@"
                         ══════════════════ 

 The "@" symbol is the code used to indicate a new topic.  The index
 facility supplied with Quikhelp uses this code as a reference to build and
 maintain the index file which allows for topical reference selection.

 The "@" symbol also indicates the beginning of a new screen page.


  ┌──────────────────────────────┐
  │  Usage :   @<topical search> │
  └──────────────────────────────┘

      Example:  @Employee Data


    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Screen Feed Hook
%blue,white

                           Screen Feed Hook "^"
                           ════════════════════

 Uses:
        1. Indicates the beginning of a new screen.
        2. Similar to a Form Feed on a printer.
        3. Allows for user-defined page breaks.

  ┌──────────────────────────────┐
  │  Usage:  ^                   │
  └──────────────────────────────┘

@Menu Line Prompt
%white,red

                           Menu Line Prompt ">"
                           ════════════════════
 Information:
        1. Indicates a Menu Item.
        2. Continuous, columnar format.
        3. Intermixed with other text on same line

  ┌──────────────────────────────┐
  │  Usage :   ^                 │
  └──────────────────────────────┘

        Here's an example of a menu using bad syntax:

    ╔══════════════════════════╗
    ║>   [First Choice   ]     ║
    ║                          ║ ───────  Menu items must be continous.
    ║>    Second Choice        ║           No empty line between choices.
    ║>    Third Choice         ║
    ║>    Fourth Choice        ║
    ╚══════════════════════════╝
^
        Now, here's an example of a menu with proper syntax:

    ╔══════════════════════════╗
>   ║>  [[First Option   ]]    ║ ───────  Menu delimiters need only be   
>   ║>    Second Option        ║           placed on the first line.
>   ║>    Third Option         ║
>   ║>    Fourch Option        ║
    ║                          ║
    ╚══════════════════════════╝



@Menu Delimiters
%black,aqua

                            Menu delimiters
                            ═══════════════  

 Quikhelp uses the menu delimiters to highlight in reverse video the
 possible options in the menu available for selection.  As mentioned above,
 these menu delimiters must be used only on the first menu selection. 
 Quikhelp takes care of the rest automatically.

    Example:
    ╔═══════════════════════╗               Delimiters must always
>   ║>  [[Add/Update     ]] ║───────────── be placed on the FIRST menu
>   ║>    Review Only       ║               item.
>   ║>    Delete            ║
>   ║>    Utilities         ║
    ╚═══════════════════════╝
^
    ╔═══════════════════╗
    ║>    Phase One     ║
    ║>   [Phase Two  ]  ║───────────── This won't work.
    ║>    Phase Three   ║
    ║>    Phase Four    ║
    ╚═══════════════════╝
 The menu item delimited is the topical reference when this item is
 selected. 

 Therefore, is stands to reason that for the menu above, there must be valid
 points of reference in the help file indicated with the "@" symbol.

        Example:
                @Phase One
                @Phase Two
                @Phase Three
                @Phase Four

 If the resulting topical reference is not found, the "No Match" message
 will appear briefly at the bottom right-hand corner of the screen, and the
 first help screen is displayed instead.

@Comment Hook
%blue,white
                              Comment Hook "*"
                              ════════════════

 As a developer, you are already familiar with the dBASE comment character,
 our friend, the asterisk "*".  You can include lines in your documentation
 which will no be displayed by Quikhelp.  

 ALL HOOKS MUST BE PLACED IN COLUMN 0.

        Here's an example:
  ╔══════════════════════════╗
  ║   >   [selection one  ]  ║
  ║   *>    selection two    ║ ───────── Comment out this line in the
  ║   >    selection three   ║            help file.
  ║   >    selection four    ║
  ╚══════════════════════════╝
                                  ╔══════════════════════════╗
>                                 ║   >   [selection one  ]  ║
> This is what  ───────────────  ║   >    selection three   ║
> you see.                        ║   >    selection four    ║
                                  ╚══════════════════════════╝
@Color Selection Hook
%aqua,magenta
                               Color Hook "%"
                               ══════════════

 ALL HOOKS MUST BE PLACED IN COLUMN 0.

 Quikhelp allows the developer to select the color for all text displayed.
 By indicating the color desired all displayed text will be output in that
 color until the next color "hook" is given. 

 Quikhelp allows you to change the colors as often as you like.

 Screen color can be changed by placing the "%" color hook at the beginning
 of a new topic or new page. An example illustrates:

        Example: New Topic                 Example: New Page

                 @Topic One                          ^
                 %white,blue                         %yellow,black
    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
^


  ┌─────────────────────────────────────────────────┐
  │  Usage:   %foreground color, background color   │
  └─────────────────────────────────────────────────┘
^

  The valid colors are:

   ╒═════════╕
%white,black
   │ black   │                                                                .
%black,white
   │ white   │                                                                .
%black,red
   │ red     │                                                                .
%black,blue
   │ blue    │                                                                .
%black,green
   │ green   │                                                                .
%black,yellow
   │ yellow  │                                                                .
%black,magenta
   │ magenta │                                                                .
%black,aqua
   │ aqua    │                                                                .
   ╘═════════╛
%blue,aqua
 Example:     %blue,aqua                                                           .
%aqua,magenta

 Default color selection is white in the event of improper spelling
 or color selection.

 Example:   %blue,magNeta ;this will result in a blue foreground and a white
                       background

@QuikHelp BOF Behavior
%white,blue
                      BOF - Beginning of File Behavior

 Here's a typical help/reference layout:

            Physical BOF
                   ╒═════════════════════╕
                   │@TOPIC A             │
                   │                     │
                   │  screen 1           │
                   │                     │
                   │@TOPIC B             │
                   │                     │
                   │  screen 2           │
                   │                     │
                   │@TOPIC C             │
                   │                     │
                   │  etc.               │
                   │                     │
                   ╘═════════════════════╛
            Physical EOF - (End of File)
^

                           Physical & Logical BOF
                           ══════════════════════
 Physical BOF is the actual beginning of the file.

 Logical BOF is the first screen of a selected menu item. This can vary from
 selection to selection. Logical BOF prevents the user from scrolling to
 screens prior to the one selected. 



    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Interfacing with Clipper
%white,magenta

 QuikHelp is written entirely in Clipper - Summer '87 version.

 In order for your program to gain access to QuikHelp directly, 
 all you have to do is link the QuikHelp.lib library at link time.


    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
^
                           Context-sensitive Help
                           ══════════════════════

 To go directly to a specified topical reference simply use the following
 syntax:

      ╒════════════════════════════════════════════════╕
      │   Usage:  qh( [helpfile.hlp], [search topic] ) │
      ╘════════════════════════════════════════════════╛
     
 Quikhelp will open the specified help file and display the first screen
 found by the topic requested.  (Now we are at the Logical BOF.)



                 Example: qh( "databex.hlp", "Operations" )
^

                              General Reference
                              ═════════════════

                      ╒═══════════════════════════════╕
                      │   Usage:    qh([helpfile.ext])│
                      ╘═══════════════════════════════╛

 Calling Quikhelp in this fashion will simply open the helpfile specified
 and display the opening screen for this file.  (The opening screen of a help
 file is typically, though not necessarily a MENU of options.)


                        Example: qh( "databex.hlp" )
^

                              Default Reference
                              ═════════════════

                          ╒══════════════════════╕
                          │   syntax:   qh( )    │
                          ╘══════════════════════╛

 Calling Quikhelp in this fashion will cause the file "quikhelp.hlp" to be
 searched for and, if found, opened and turned to the first page of the file.
        
                                Example: qh()
@Interfacing with Dbase
%blue,white
                              Quikhelp & dBASE
                              ════════════════
 Quikhelp is optimally designed to work best with Clipper Summer '87
 version. However, you may write a short program, including the necessary
 Quikhelp functions and parameters, compile it with Clipper and Run/! this
 from inside of any other package database or otherwise that is capable of
 running a DOS shell from within that package.
       
                ╒══════════════════════════════════════════╕
                │  Usage:  run [yourprog]                  │
                │     or:  ! [yourprog]                    │
                ╘══════════════════════════════════════════╛

 This is obviously a quick and simple solution that will work given enough
 available memory to load and run "yourprog".

 Quikhelp has been designed specifically to work in conjunction with
 Clipper.  Working with any other program is simply an added bonus.
    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Calling From Dos
%yellow,black

                               Quikhelp & DOS
                               ══════════════
 Quikhelp can be operated from DOS by again writing a small program in
 Clipper including any necessary references to help files and topics, and by
 simply running the resulting Clipper/Quikhelp  .EXE file directly from DOS.

 (Unofficial Note:)
 We might suggest making a generic enough Clipper program utilizing the
 Quikhelp library to allow testing of all documentation while in the actual
 editing/integrating phase.  How?  Hint: try a macro or two.

 A virtual endless array of uses are available.  However, remember, Quikhelp
 has been designed to work with Clipper.  Any other uses are simply added
 bonuses.

    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Debugging
%green,red

                               Instant Replay 
                               ══════════════

 While incorporating existing documentation into a newly developed Quikhelp
 reference file of your choice, all of the textual edits are available
 immediately when viewing the help file under Quikhelp.

 In order to see the color, layout or other elements of your documentation
 try using a simple generic version of a Clipper/Quikhelp program. See
 "Unofficial Note:" under  Quikhelp & DOS section above.

 Since the exact byte offset of the topical references are critical for
 proper menu item searching, be sure to delete the corresponding ".QHX" file
 so that Quikhelp can automatically generate a new, up-to-date index file.

    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Editors
%black,white

                              ASCII Help Files
                              ════════════════
 Quikhelp operates only with pure ASCII text files, both for the help file
 which you provide and for the index file Quikhelp generates automatically.
 Any text editor, used in pure ASCII TEXT mode, will suffice. 

 Since the help files are ASCII, this provides you the distinct advantage of
 updating the documentation from time to time or even allowing the end user
 to maintain/update any help information.

 Also as an added convenience, if the text editor or word processor supports
 a page size facility, by setting the page size to 22 lines per page, you
 will be able to produce exact frames of the text Quikhelp will display.  Of
 course, in Quikhelp you will have menus, colors, borders, and a display line
 to enhance the overall picture.  But the text will look the same.
    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
^
 Quikhelp can display the full range of IBM ASCII characters.
 Simply include them in the help file, Quikhelp takes care of the rest.

                Example:   ▒░▓ ■ ∞ ε ± ÷ √ ⌡ ⁿ Æ ½ ¿ φ ≤≥ Ω
                                     or
                            Example:      

@Help File Structure
%white,black

 Quikhelp provides you with the freedom to tailor your help file to meet the
 specific application.

 The following guidelines are simply suggestions on how you may quickly
 obtain the most professional results with Quikhelp.  
^          
           ╒═════════════════════╕ Physical BOF
           │@Main Menu           │
           │    Topic Option 1   │
           │    Topic Option 2   │
           │    Etc.             │
           │@Topic 1             │                   ╒═════════════════╕
>          │    Screen 1         │                   │  [Main Menu 1]  │
>          │    Screen 2         │                   │   Main Menu 2   │
           │    Screen 3         │                   ╘═════════════════╛   
           │@Topic 2             │                      
           │    Screen 1         │
           │    Screen 2         │
           │    Screen 3         │
           │@Topic 3             │
           │    Screen 1         │
           │    Screen 2         │
           │    Screen 3         │
           │    Etc.             │
           │                     │
           │   Menu Option 1     │
           │   Menu Option 2     │
           ╘═════════════════════╛ Physical EOF
^
                             The Suggested Ideal
                             ═══════════════════

 Typically the first should screen should contain a front-end menuing system
 for the entire help file currently loaded.  Since there is no limit to the
 number of screens or menus in a help file, theoretically the first menu
 could present a choice of 22 menu items.  These menu items could in turn be
 nothing more than other menus with additional choices of up to 22 choices as
 well.  These additional 22 choices could in turn be menu items, etc.  The
 possibilities are virtually endless.  There is certainly no inherent limit
 to the number of "nested menus" or "choices" that can be created.  There
 probably is a practical limit which will be determined by the
 help/reference file itself.

 A few words of caution:
 The last screen at the Physical EOF should have a menu reference to
 somewhere, preferably the opening screen.
    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@QHindex
%blue,aqua

                              Quikhelp Indexing
                              ═════════════════
 Quikhelp provides automatic indexing of topics within a help file whenever
 a related ".QHX" file is not present.  INDEXING IS AUTOMATIC.

 However, the function QHINDEX() is provided in the Quikhelp Library and
 can be called as follows:
                      ╒══════════════════════════════╕
                      │  Usage: QHindex(helpfile.ext)│
                      ╘══════════════════════════════╛

 This function will build an index file with the same name of the help file
 and add the extension of ".QHX".  The ".QHX" is automatic, mandatory and
 cannot be overridden.
    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@QuikHelp Screen Structure
%aqua,black

 Line 0  ╒═══════════════════════════════════════════════════════════════╕
         │                                                               │
 line 2  │ ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| │
         │                                                               │
         │                                                               │
         │                                                               │
         │           Maximum of 22 lines of text displayed here.         │
         │                                                               │
         │                                                               │
         │                                                               │
         │                                                               │
         │                                                               │
         │                                                               │
         │                                                               │
         ╘═══════════════════════════════════════════════════════════════╛
 line 24  ------------------ Quikhelp Display line ----------------------

    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
^
                        Quikhelp Supplied Formatting
                        ════════════════════════════
 Each Quikhelp screen displays a full screen of 22 lines of help text per
 screen, a border, screen title (if available), and a QuikGuide line at the
 bottom of the the screen.

 The QuikGuide Line at the bottom of the screen provides the user with the
 necessary instructions to move above about, once inside the Quikhelp system.

 In addition any other messages such as "Searching", "No Match", etc. are
 also displayed on the last line of the display.

@Search Topic
%aqua,magenta

 Screens and Menus can be searched via a "topic".  Search topics are defined
 by using the "@" hook.  The maximum length of a search topic is 127
 characters.  Any mixture of upper, lower case, punctuation, spaces, or
 numbers may be used to create a valid search topic.

 Here's an example of some valid search topics:

                 ╒══════════════════════╕
                 │ Search A             │
                 │ Search-B             │
                 │ "Search A"           │
                 │ Search 1.1           │
                 │ Topic Utility Guide  │
                 │ guide1               │
                 │ GUIDE1               │
                 │ Guide1               │
                 ╘══════════════════════╛              ┌─────────────────┐
>                                                      │  [Main Menu 1]  │
>                                                      │   Main Menu 2   │
                                                       └─────────────────┘
^

 ALL HOOKS MUST BE PLACED IN COLUMN 0.

 Column 0─┐
          │
          
 Example: @Employee Data


      ┌──────────Employee Data───────────┐
      │                                  │
      │           First Screen           │
      │                                  │
      └──────────────────────────────────┘


^

                           Search Topics & Clipper

 Usage for the search topic under Clipper:

                      ╒══════════════════════════════╕
                      │  QHtopic("Search topic")     │
                      ╘══════════════════════════════╛


@Example of Use
%red,white

 Quikhelp will assume a default help file name of "Quikhelp.hlp" if none is
 given.  However, any file and any valid DOS file name may be opened as a
 Quikhelp help file.  Only one help file may be open at a time however.






    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
^

                                  Example  
                                  ═══════  
  The following example shows how an application in dBASE can provide help
 to several different levels of users depending on each user's level of
 expertise.



  novice = .t.
   if novice 
        ! novice.exe (Clipper created)
   else
        !qh expert.exe (Clipper created)
   endif

    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘
@Error Messages
%aqua,black
                                Error Message
              ╒═══════════════════════════════════════════════╕
              │  "QuikHelp file cannot be opened: <helpfile>" │
              ╘═══════════════════════════════════════════════╛
 Probable Causes:
        1. Help file doesn't exist.
        2. File damaged.
        3. Out of available file handles or memory to open
           another file.
                                Error Message
                               ╒═════════════╕
                               │ "No Match"  │
                               ╘═════════════╛
 Probable Cause:
        1. Invalid Help Search Topic.
        2. Index file not up to date.
           Remedy: Simply delete the ".QHX" file associated with the
           help file used.  Quikhelp will automatically rebuild a new one.
                                             ┌─────────────────┐
>                                            │  [Main Menu 1]  │
>                                            │   Main Menu 2   │
                                             └─────────────────┘



@Versions 1.5/2.0 !!
                     ** "C" Enhanced QuikHelp **
    That's right, a "C" enhanced version!  

    The previous version, Beta Release 1.0 and the current version
Release 1.1 are both written entirely in Clipper Summer '87.  Being
Clipper purists, we took this approach first for two reasons: First,
and foremost we know Clipper better; and second we wanted to
demonstrate that a powerful, full-featured, integrated library could
be developed entirely in Clipper *without* resorting to Assembly or
"C" language routines.

    However, as developers we want four things: Accuracy, Speed,
Speed, and still more Speed!  So, in the design stages right now are
two versions scheduled for release in January 1989.  First, the "C"
enhanced version of QuikHelp (Release 1.5) which will maintain much
of the original Clipper code but will use an assembler routine for
direct video writes for *BLAZING* screen I/O, and either some "C" or
assembler algorithms for still faster searching and indexing.
                                             ┌─────────────────┐
>                                            │  [Main Menu 1]  │
>                                            │   Main Menu 2   │
                                             └─────────────────┘
@Release 2.0


    The step beyond mixing Clipper with "C" and assembler takes us to
the quintessential QuikHelp version:  a linkable library written
entirely in "C" and Assembler, *plus*  a stand-alone executable
version of QuikHelp for non-Clipper related reference facilities.


                                             ┌─────────────────┐
>                                            │  [Main Menu 1]  │
>                                            │   Main Menu 2   │
                                             └─────────────────┘

@The Wish List

    Based on user feedback during the Beta period, the following
items have been suggested for incorporation into future releases of
QuikHelp:

              o  User-definable Screen Sizes
              o  Scrolling within a page
              o  Incremental Searching
              o  Faster Indexing
              o  Faster Searching
              o  Automatic Text to QuikHelp Conversion
              o  On-line QuikHelp Editor 
                 ( Use QuikHelp to update the Quikhelp File! )
              o  Norton-Guides File Compatibility
                                             ┌─────────────────┐
>                                            │  [Main Menu 1]  │
>                                            │   Main Menu 2   │
                                             └─────────────────┘
@Free Support Policy

    Because QuikHelp has been developed using the K.I.S.S. concept,
there has been only a minimum of support required.  However, as its
complexity and range of utility increase, so, we anticipate, will its
amount of required support.

    As a small (currently three person) development company, we
simply do not have the resources to provide a separate support team. 
We *ARE* the support team, the development team, the secretarial
team, the marketing team, the research team, etc..   Consequently, we
will provide *FREE* unlimited developer support, to all *registered*
users, on a returned call, reversed charges basis.  

    Our voice mail service is available 24 hours a day, 365 days a
year.  *Every* call is returned as quickly as possible, during normal
business hours (PST).  A personal, extremely knowledgable (after all,
we wrote it!), support person will do everything possible to assist
you with your request. 
^
    In addition, we maintain an Electronic Mail Box with MCI Mail
that is also available.

                    MCI Mail Box # ...: 650-318-9786
                    24-Hour Voice mail: (619) 542-1200
                                             ┌─────────────────┐
>                                            │  [Main Menu 1]  │
>                                            │   Main Menu 2   │
                                             └─────────────────┘
@Trademarks
%red,aqua

 IBM is a trademark of International Business Machines.
 dBASE is a trademark of Ashton-Tate 
 Wordstar is a trademark of Micropro Inc.


    ** A Little About DataBex **

    Since 1982...

    We have been designing, developing and supporting business
applications and systems on microcomputers in the United States since
1982 and internationally since 1984.

    ┌─────────────────┐
>   │  [Main Menu 1]  │
>   │   Main Menu 2   │
    └─────────────────┘

