Index lookup Bug (None Specified)
At 17 AUG 1999 11:54:40AM David McGehee wrote:
The IXLOOKUP even at 3.7.2 still goes to debug if the lookup retrieves more than 64k. I get a variable exceeds maximum length in IXLOOKUP & get the debugger. I haven't tried it with earlier versions, but according to "stuff" I have read, the problem was fixed in 3.6. I don't even get a "list truncated" message, just the 'exceeds' and the debugger. The BTREE.EXTRACT routine allows multiple calls for large lists, why not the IXLOOKUP?
At 18 AUG 1999 04:02PM Stephen Revelation wrote:
David,
We attempted to reproduce a similar situation here, but unfortunately did not receive the same behavior.
Here's what we did:
1. Created 50,000 records. Each with 10 data fields (not including the key).
2. Created a B-Tree index on the key (for numeric reasons).
3. On a form containg the key and the fields, we created a button which ran an Index Lookup quick event on the 'CLICK' event.
4. The lookup, when ran on a Win98 workstation, listed by the key indexed and returned the key and the field (same) indexed. We received the 'truncating message' after the first 19,800 (approximately) were listed.
5. Entering a number greater than this number (~19,800) and less than 5,001, though not listed due to trucation, returned the indexed data.
Is this not a similar situation to what you are encountering? Any additional data to help us reproduce would be great.
-Stephen
At 19 AUG 1999 09:15AM David McGehee wrote:
Using the QBF, the same query works (returning the truncated message). However, using the IXLOOKUP function quick event for a button still bombs the IXLOOKUP. I will try a modification to the associated popup definition to lessen the fields in the popup. If all you were popping up was the list of keys, that might be the answer to why your test worked. This is demographic data queried by zip with the popup containing name/street/zip. I will try to just display the useless-by-itself zip and see if it quits abending.
At 19 AUG 1999 11:17AM Stephen Revelation wrote:
David,
The reason I said the IXLOOKUP only displayed keys was to point out that over 64k of data form one dictionary item was accessible at one time.
We actually bumped the amount of records up to over 70,000 records and performed the IXLOOKUP queried by key and returned a popup of key, {field1}, {field2}…..to {field5}. This was tested successfully with the truncation message on both Win98 and WinNT40 workstations.
The QBF funcitionality also worked as expected, in-line with your QBF results.
-Stephen