Internal Error #1256, __DBSETIND(0)

  (#112199) There were indications that:

  USE GLOBAL
  i1 = "globuser"
  SET INDEX TO &i1

  causes this error, when both database and index exist.  I was unable to
  confirm this.

  (Mail: Del Texley [71117,3551])  Del found that this error may be related
  in some way to the size of the database.  He says that the workaround is
  to test the number of records before opening the index file, and recreate
  it if less than 5 records exist.

  SELECT( SEL_POST )
  USE PRPOST INDEX PRPOST   // Crash here with internal error # 1256 if
                            // prpost is empty!

   ** This Fixes if substituted for above line
   USE PRPOST
   IF RECCOUNT() < 5
      INDEX ON PRPOST->Emp_num + DTOS( PRPOST->Pdate )  TO PRPOST
   ELSE
      SET INDEX TO PRPOST
   ENDIF
   ** Weird enough for you?

  (#112378) This message reports that 1256 occurs during a SET INDEX.  The
  user says that he was using an index expression that contained a UDF for
  displaying percent done during the index.  Clipper 5.0 stores index exp-
  ressions as it receives them: "INDEX ON A     + B" will keep the strange
  spacing.  His problem was that he had a function that was messing with
  the NTX header, and not taking this  into account.