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

  SIx Driver Memo Files:

  The SIx Driver's SIXCDX flavor uses FoxPro-compatible memo files (.FPT's)
  for storing data for memo fields.  The SIx Driver's SIXNSX flavor uses a
  different memo file format which uses an .SMT extension.  Both SIx Driver
  memo file formats use a default block size of 64 bytes.  This block size
  can be changed to any multiple of 16 from 16 to 1024 bytes.

  SIx Driver memo files can be used to store any type of data.  While the
  standard Clipper/dBASE III+ .DBT memo uses an end-of-file marker (ASCII 26)
  to mark the end of a memo entry, .FPT and .SMT memo files store the length
  of the entry.  This not only eliminates the problems normally encountered
  with storing binary data in a memo field, but also speeds up memo field
  access since the data doesn't have to be scanned to determine the length.

  You can also store Clipper arrays (even multi-dimentional ones) in an
  FPT/SMT memo field.  it's as easy as:

     /*---( Assume TEST.DBF has a MEMO field called NOTES.SMT )---*/
     USE bogus VIA "SIXNSX"
     aFiles := Directory()       // Store File Directory array to aFiles
     ? ValType( test->NOTES )    // Returns: "M"
     test->NOTES := aFiles       // Store array in NOTES memo field
     ? ValType( test->NOTES )    // Returns: "A"

  And getting the array back out of the memo field is just as easy...

     aMyArray := test->NOTES     // POOF!!!  You've got it!


  The SIx Driver can optionally support normal Clipper memo files (.DBT's)
  instead of .FPT's.  To enable .DBT support add DBT.OBJ as a file to your
  link command or link script.  For example, using the SIXNSX flavor:

    EXOSPACE FI myapp,myfuncs,sixnsx,dbt LIB six3,clipper

  or

    BLINKER FI myapp,myfuncs,sixnsx,dbt LIB six3,clipper

  or

    WL32 myapp myfuncs sixnsx dbt,,, six3 clipper