Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!prlb2!kulcs!kulesat!esat!lily
From: lily@haydn.kulesat.uucp
Newsgroups: comp.databases
Subject: Problem with Clipper a'86
Message-ID: <1081@haydn.kulesat.uucp>
Date: 25 Apr 89 09:23:50 GMT
Organization: Katholieke Universiteit Leuven,ESAT - dep. Elect. Engineering, Belgium
Lines: 57


Hi there, 


Are there any Clipper-guru's around to help me with a small problem ?

Yes indeed, I do have a problem with Clipper. I also have found a way
to work around it, but i'm not really satisfied.

In an accounting application I wrote some time ago, the DBF-files
have become very big (several hundreds of Kbytes). Accordingly
the NTX-files are also rather big. Now, sometimes when SEEK-ing a
record (with the right index file opened) Clipper can't find it.
Found() becomes .F. although I'm perfectly sure that the record is
in the database.  I tried solving the problem by REINDEX-ing, but
it didn't work. Next I tried LOCATE-ing the record. This workes
fine, but it takes a very long time.  For the moment I've put up a
construction like this :

      .
      .
      .
      SEEK a_certain_index_value
      
      IF .NOT. found()
        **
        ** I'm pretty sure the record is in the database, so look again
        **
        @ 23, 20 SAY "Trying to locate the record ..."
        LOCATE FOR index_field = a_certain_index_value
        
        IF .NOT. found()
          @ 23, 20 SAY "Sorry record not in database."
          .
          .
          .
        ENDIF
      ENDIF
      .
      .
      .

It seems very funny, but sometimes the LOCATE-message appears, and
sometimes the SEEK seems to work. Now this is very annoying, and I would
like to know if you know of a good solution. This all happens when using
Clipper version Autumn '86. HELP !!!

Dirk.
LILY.

Katholieke Universiteit Leuven
     E.S.A.T.  -- M.I.2
           BELGIUM
           

UUCP    : kulesat!lily
BITNET  : lily%kulesat.uucp@blekul60