Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 10 FEB 1998 02:00:11PM Jeff Blinn wrote:

A discovery we did make - if I replace $XREF.BROWSE with the copy from our 2.12 version - this problem is eliminated.

I'm wondering at this point if this has something to do with 'SPINDEX'? In the 2.12 system there is no sign of it - it is showing up in the 3.12 version. (Object code contains things like SPINDEX.COMMON, and other references to SPINDEX.)

Would replacing $XREF.BROWSE have any other ramifications? Is there a better way to fix this?

Thanks,

Jeff


At 11 FEB 1998 08:53AM Aaron Kaplan wrote:

This message might help you.

As for the change from 2.12 to 3.12, there were some heavy changes in internal index structures from 2.12 into 3.12. A noticable one is the change from field.XREF to field_XFREF. While most of the system in 3.12 is smart enough to try both, I wouldn't assume anything.

apk@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 12 FEB 1998 02:27PM Dave Bennett wrote:

I found that a long time ago someone installed Spindex, we are at 3.111 and to stop the message but allow the user to search I made a subroutine called XSHOVALS and placed in SYSOBJ.

EXPENDABLE SUBROUTINE XSHOWVALS(INFO)

SWAP '*' WITH @FM IN INFO

INFO=INFO

INFO=DELETE(INFO,4,0,0)

SWAP @FM WITH ',' IN INFO

CALL CATALYST("V",INFO)

RETURN

This has been in place for more than 8 monthes and working great.


At 13 FEB 1998 04:22PM Jeff Blinn wrote:

Dave - thanks for the code. I've added it to the system and it takes care of the problem! Much better than trying to find all the indexed fields, that aren't on the screen, etc.

Thanks again,

Jeff

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/74d5412ca964a4b5852565a70068631d.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1