Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Advantage CA-Clipper Guide v6.11 - <b>ca-clipper with tps behavior changes</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
   CA-Clipper with TPS Behavior Changes
------------------------------------------------------------------------------

   Some CA-Clipper commands and functions have slight behavioral changes
   if they are used during a transaction. If the functionality of these
   commands and functions were not modified during a transaction, the
   transaction would not function properly. These operations can be
   issued during a transaction, however, the results may be different
   than expected. Please note the differences below:

   RLock()

   The RLock() function, when used during a transaction, does not unlock
   any previously locked records. Instead, it works like the dbRLock()
   function, which locks the current record but does not unlock any
   previously locked records. This is because the corresponding updates
   to those records/files cannot be made during the commit phase if they
   are not locked.

   APPEND BLANK and dbAppend()

   APPEND BLANK and dbAppend(), when used during a transaction, do not
   unlock any previously locked records. This is because corresponding
   updates to those records/files cannot be made during the commit phase
   if they were not locked.

   GOTO an Appended Record

   If a GOTO nRecordNum operation is performed, and nRecordNum is being
   appended by another application during a transaction, the user will
   be positioned to "lastrec + 1" and the EOF will be set to .T.. This
   behavior exists because records appended during another transaction
   are "invisible" to all other users until that transaction is committed.


Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson