[<<Previous Entry]
[^^Up^^]
[Next Entry>>]
[Menu]
[About The Guide]
NETWORKS Seeks and Indexing comments.
Clipper Version 1.29 dtd 04/15/91.
Problem Statement per Darren DeLoach [76264,1042]
1) A bug exists which can result in failed SEEK statements on a
workstation whenever _another_ workstation on the network edits the
logical top record in the file to have a new index key which moves it
in the index such that it is no longer at the logical top-of-file.
Other stations do not see the new index value in the NTX pages, and so
incorrectly perform SEEKs in the file. The problem only occurs with
the logical first record in the file; adding new records does not cause
the problem, even if you are adding the first record in the file.
2) General comment on indexing (see workaround #2).
Cause
1) Unknown.
2) N/A
Work Around(s)
1) Setting SOFTSEEK ON seems to make SEEK perform correctly. A GO TOP
before the SEEK worked in one specific case, but is not guaranteed
to work in all situations.
2) A user has reported that the following methodology has eliminated
problems he was having with indices:
Lock the File
Index the File
Close the Index
UnLock the File
Set Index to ...
This page created by ng2html v1.05, the Norton guide to HTML conversion utility.
Written by Dave Pearson