{{tag>category:"OpenInsight" author:"rayc@symmetryinfo.com" author:"[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]" author:"Mike Ruane" author:"Don Miller - C3 Inc."}}

[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]


==== Can't Add Relational Index (OpenInsight) ====
=== At 28 AUG 2001 08:32:27PM rayc@symmetryinfo.com wrote: ===
 
 
<QUOTE>
To all,

I am simply trying to put an relational index on a File that was converted from AREV.



I followed the direction in the OI native table document. After filling in the data and clicking "ADD", I get the below message:



[b]SSP78 Different sort modes '""' and 'TOP' are not allowed for many to one relational indexes.[/b]



I get the same message regardless of sortmode (beginning, end, ascend left, ascend right, etc.)



I'm using OI 3.74. Thanks,

Ray Chan



P.S. Posted to otherside as well.



rayc@symmetryinfo.com onmouseover=window.status=imagine ...  ;return(true)"

[url=http://www.symmetryinfo.Com" onMouseOver=window.status=Imagine ... ' ;return(true)]Symmetry Info[/url]

Ray Chan ~ Symmetry Info
</QUOTE>
----

=== At 29 AUG 2001 04:51AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>What - the [b][i]Dark[/i][/b] side?



[url=http://www.sprezzatura.com]The Sprezzatura Group[/url]

[i]Universal Leaders in all things RevSoft[/i]

[img]http://www.sprezzatura.com/zz.gif[/img]

</QUOTE>

----

=== At 29 AUG 2001 07:22AM Mike Ruane wrote:  ===

<QUOTE>Ray-



Sounds like one of the dictionary records still has the old sort mode stored in it. Edit both dictionary fields in the Editor and remove any indexing information, and try again.



Mike

</QUOTE>

----

=== At 29 AUG 2001 03:50PM rayc@symmetryinfo.com wrote:  ===

<QUOTE>Mike,



[i]Sounds like one of the dictionary records still has the old sort mode stored in it. Edit both dictionary fields in the Editor and remove any indexing information, and try again.[/i]



I found indexing data in the dictionary of the target field in the target file, e.g.,



Target File:

Line 24: Source_File_Name*Item_To_Be_Add_To_Target_Field



I deleted the above line. Nothing was found in the source.



After I added the Relational index back, the dictionary for the source file showed:



Line 23: Targe_File_Name*Target_Field*BOT



Based on your comment above, is "BOT" an "old" sort mode. Is this incorrect for OI? Hope this is okay as I just let OI do its thing.



Also, I ran into some unusual behavior when adding/rebuilding relational index.



When I ADD the relational index, I got the following Runtime Error message:



ENG0024: Build Index, Line 1 divide by zero. Result of zero!



In debugger, message displayed:  



To make sure things were clean, I went to REMOVE the index so I could start over. The "hours glass" was up for a long time and I could see that nothing was happening. So I closed down OI using W2K's Task Manager.



Then I went back to Adding the relational index. This time when I got the Build Index error message I went to REBUILD index. After I select REBUILD, the progress bar stays at 0 percent and the debugger was in background. I killed everything again.



I read up on Relational Indexing on this site. Some people stay away from it. Is Relational Indexing better today? Any reason I am getting the Build Index error messages?



Any comment on this and above questions would be appreciated,



Thanks,

Ray



P.S. Sorry if this is jumbled, but what a day!







rayc@symmetryinfo.com onmouseover=window.status=imagine ...  ;return(true)"

[url=http://www.symmetryinfo.Com" onMouseOver=window.status=Imagine ... ' ;return(true)]Symmetry Info[/url]

Ray Chan ~ Symmetry Info



</QUOTE>

----

=== At 30 AUG 2001 09:15AM Don Miller - C3 Inc. wrote:  ===

<QUOTE>Ray ..

BOT is Bottom To Top.  It's valid in OI and AREV.  Relational Indexes are a bitch.  Once you get them set correctly, they seem fine.  When importing data from versions of AREV into AREV 3.12 (or 3.x), sometimes Relational indexes get totally messed up.  I usually remove all indexing from all tables before bringing them into AREV / OI.  If the data to be indexed is Right Justified with a data type of some numeric (INTEGER, etc.) and you bump up against data that doesn't meet this criteria, you'll get a bad index.  The problem is that you don't know which one it is.  I usually have to check to make sure that all dict elements that are to be indexed and numeric are numeric.



Don Miller

C3 Inc.

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=E1B34A7FD2A0667F85256AB70002F8B9|View this thread on the Works forum...]]