btree.extract on .xref returning bad results (AREV Specific)
At 05 OCT 1998 02:59:55PM L. Woody Woodbury wrote:
I have a report that performs a btree.extract on a multivalued field, AP.OPEN.XREF (which is obviously crossreferenced). Seemingly every month or so when this report is processed, the results are incomplete. It will list a truncated group of records. A TCL Select will give correct results and rebuilding the crossref index on AP.OPEN will also then give correct results. What is causing the error? Any clues?
L. Woody Woodbury
Programmer
Fulcrum InteTech
wwoodbury@fulcrumit.com
At 05 OCT 1998 03:28PM Victor Engel wrote:
How many hits are you talking about? Don't forget that BTREE.EXTRACT is limited to 64K of hits. If the results exceed this, it will tell you. Do you test for this condition?
At 06 OCT 1998 12:24PM Terry Rainville wrote:
When you make a firld XREF the computer will create an XREF
for that field with a _XREF extention.
ie.
TEST
TEST_XREF
All btree lookups must be done on the _XREF field.
At 06 OCT 1998 03:19PM L. Woody Woodbury wrote:
I have code to trap for 64K limit and that is not it. And why if I rebuild the indexes does it work? Any other ideas?
At 08 OCT 1998 10:53PM Arev 2.1 programmer wrote:
I've had a similar problem. It was due to the case sensitive setting for the btree indexed field.