""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
   DBASE ARCHIVE FILES IMPROVE PERFORMANCE
   """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
   PRODUCT   :  R:BASE                  VERSION      :  3.1
   CATEGORY  :  SPEED & PERFORMANCE     SUBCATEGORY  :  ARCHIVES
   """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
   You can add a lot of speed to your R:BASE 3.1 applications by reducing
   the amount of data R:BASE has to process. If you have some data that
   you only use once or twice a year, you can improve the speed of your
   applications by archiving the infrequently used data into dBASE files.
   Then the data will be out of your database, but you can still attach
   the dBASE files when you need them.
 
   For example, you could put 1988 transactions into an ARC1988.DBF file
   and 1989 transactions into ARC1989.DBF. Then if you need a report that
   includes that data, you can simply attach the dBASE files to your
   R:BASE database and then create a view using UNION SELECT (a form of
   the SELECT command) to include the archived rows in the view. Then
   base the report on the view.
 
   You don't even have to own dBASE. You can use the programs published
   in Wayne's Corner in the March/April 1991 EXCHANGE. Download
   MRIM0291.ZIP. The program MAKE_DBF.CMD is inside it. MAKE_DBF.CMD
   creates a dBASE file from inside R:BASE.