Index lookup problems (AREV Specific)
At 10 JUN 1998 08:45:04AM John Bouley wrote:
FYI,
A customer came to me with a problem looking up certain values in an index called City_xref. They were looking for all customers in "ORLANDO". The Btree.extract returned zero records. A select on City_Xref returned 65 hits! I followed the indexing data throught the tree and "ORLANDO" was in the index in the correct location.I noticed that the customer was using Arev 3.1. Therefore, I installed the Arev 3.12 update. This fixed the problem! However, it caused others. I found that after installing the 3.12 update all lookups that were using ".XREF" no longer worked. I had to convert all ".XREF" to "_XREF". Also, some screens that previously worked now had field position problems. The fix for this was to call the window up and press F9.Did anyone have a similar experience?
At 13 JUN 1998 03:12PM Aaron Kaplan wrote:
ARev 3.1 had some interesting indexing problems so I'm not at all surprised that 3.12 fixed them.
The .xref/_xref stuff is pretty weird. 94% of the time, these are updated without troubles. The other 6% of the time, there is nothing but troubles. I was able to trace through in the code what was happening after the fact, but was never able to find when it was happening in the upgrade to fix it. The code in xref.browse that's can't handle the .xref ended up with problems. I can't remember all the details anymore (the memory thing) but just doing
If IndexField-5,5=.XREF' then
IndexField-5,1=_'
End
just didn't work. A few other things caused some problems.
Only solution was to remove and rebuild.
The screen bit was almost the same sort of thing. It's related to hidden labels. All that you need to do is unhide the labels and rehide them. Don't remember if a save was involved in between. I could never find the real difference between the before and after versions and was unable to release a patch.
