Click above to get retro games delivered to your door ever month!

  How do I use the SIx Driver with an existing application?:

  Getting started with the SIx Driver is simple.  The following steps will
  get you up and running with your current application:

    NOTE:  The text below uses the SIXNSX flavor of the SIx Driver for the
           examples.  If you are using the SIXCDX or SIXNTX flavor instead,
           simply substitute the appropriate RDD name instead of "SIXNSX".


  1. Add the appropriate SIx Driver header file to each source code file
     where database support is required.  For example:

         #include "SIXNSX.CH"


  2. Make sure index extensions aren't hard-coded in your application.

     The default extension for SIx Driver indexes under SIXNSX is .NSX.
     Under the SIXCDX flavor, the default index extension is .IDX.  As
     with CA-Clipper's DBFNTX driver, our SIXNTX driver also uses the .NTX
     index extension and format.

     The best way to determine index extensions from within an application
     is to call Clipper's OrdBagExt() function.

     For example, if you use the following code to determine the existence
     of an index file:

          IF !file("INDEX.NTX")
            INDEX ON field TO index
          ENDIF

     you should change the code to use Clipper's OrdBagExt() function
     instead, as follows:

          IF !file( "INDEX" + OrdBagExt() )
            INDEX ON field TO index
          ENDIF


      NOTE: Under Clipper 5.01a, the OrdBagExt() function was known as
            IndexExt().


  3. Add SIXNSX.OBJ to your link command or link script.  This will make
     the SIx Driver's SIXNSX flavor the default RDD.  (Place SIXNSX.OBJ
     after your main application files.)

  4. If your application uses memo fields, add DBT.OBJ to your link command
     or link script to add .DBT support until you get a chance to convert
     your .DBT's to .SMT/.FPT's (optional).  Converting .DBT memo files to
     .SMT/.FPT's is covered elsewhere in this section.

  5. Add SIX3.LIB as a library to your link command or link script.  If you
     are using Blinker, you can overlay most of the SIX3.LIB file simply by
     specifying the SIX3.LNK link script, like this:

        BLINKER FI myapp,sixnsx,dbt @six3 LIB clipper

  That's it!  You've converted your application to use the SIx Driver's
  high-performance index format.  Now you can start to make use of the SIx
  Drivers extended features, such as compound indexes, index scoping,
  roll-your-own indexes, ...