Internal Error #5320, __DBCREATI (0)

  (#94001) Index Problem.

  (#96249) Sometimes solved by reducing index key size.

  (#95342) Possibly a conflict with CACHE, VDISK, or SMARTDRV.

  (#95701) More of the same - May not be CACHE - perhaps combination of
  key length and available memory.

  (#95087) Indexing may have problems with macros.  Try surrounding your
  key expression with parenthesis.

  (#101629) Suggests that perhaps not pre-linking with BASE50 will help.

  (#108574) One user appended a CHR(0) to the end of his key string at
  Nantucket's suggestion, and this error went away for good.

  (#112220) Reports that this error occurred also during a SORT -D in
  __DBARRANG(0).  No resolution was offered.  Try the sort in a stand alone
  program - the problem may be related to the size of the DBF and available
  memory.

  (#112803) This error seems to occur when clipper thinks you have expanded
  memory, but you do not.  Installing expanded memory has been known to
  solve it.  No guaranties, but it could be worth a try.  It also seems
  Smartdrv.sys is usually installed at the time.

  (#112960) In essence, the 5320 means the VMM has tried to map an EMS
  page when no EMS is available or that the EMS manager has returned an
  error code.

  () Most of the 5320 reported errors have been on INDEXing or SORTing
  operations.  (PACKs with NTXs open, REPLACING a key field, etc...)  Since
  5320 is in the VMM error range (53xx), this would indicate that 5320 has
  something to do with indexes related to VMM.  VMM is used for buffers,
  variables, and clipper code.  It should be noted that 53xx does not
  necessarily mean that there is a low memory problem - any VMM problem will
  do.

  (Mail: 71660,1440) While installing a Clipper 5.0 program on a Novell     ~
  Network, this user solved continuous 5320 errors by switching from DOS 3.3
  to 4.x.  I personally believe that the switch in DOS versions was not the
  deciding factor, and that perhaps a change in EMS Driver or General RAM
  configuration during the OS switch caused the errors to disappear.

  (#117235) Ray Crisp [73667,1450] solved his 5320 woes by changing the     ~
  following code:

  SELECT 1
  USE ARTRANS
  INDEX ON VndNo+FileNo+STR(TransNo) TO ARTRANSA
  INDEX ON FileNo+STR(TransNo) TO ARTRANSF
  CLOSE DATABASES                        // Ray Added this, and ...
  SELECT 1                               // this, and his problems disappeared
  USE ARFILE
  INDEX ON FileNo TO ARFILE
  // etc ...

  (#115909) Kurt Schaldenbrand [72137,2703] suggests that this error is     ~
  related in some way to expanded memory: "When a customer adds expanded
  memory, occurrences of both 416 and 5320 go away."