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

   Server Advantage Optimized Filter APIs

   Advantage has support for creating and using Advantage Optimized Filters
   on the server as well as on the client.  Versions of the Advantage
   CA-Clipper Libraries before 5.0 only had support for building and using
   AOFs on the client.  AOF usage on the client is more flexible than AOF
   usage on the server, but AOF usage on the server is much faster than
   AOF usage on the client.

   Server AOFs are physically built and used on the Advantage Database
   Server.  Because the index files are physically located on the server,
   the building of Server AOFs is much faster than the building of
   Client AOFs.  Server AOFs are evaluated on the server.  When performing
   a movement operation, only the result record that passes the AOF filter
   condition is passed back to the client application.  Depending upon
   server CPU speed, network speed, and whether an index order is active
   or not, Server AOFs can be up to 10 times faster than Client AOFs.

   The only APIs that can manipulate or retrieve information about Server
   AOFs are the APIs listed in the following section that begin with the
   prefix "AX_".  The Client AOF APIs begin with an "aof" prefix and cannot
   be used to manipulate or retrieve information about Server AOFs.

   Server AOFs are located in the Advantage RDD library, DBFAXS.LIB.  If
   your application uses Server AOFs only, AOF.LIB does not need to be
   linked into your application.