STILL HAVING BTREE INDEXING PROBLEM (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|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]]


==== STILL HAVING BTREE INDEXING PROBLEM (AREV Specific) ====
=== At 08 OCT 1998 08:31:51PM AProgrammer wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
Please refer to my message dated 10/2/98.

   After checking everything suggested (i.e., key field length, trailing delimiters,

and removing all MFSs except the SI.MFS), I then deleted the table and 

dictionary and recreated both.  I rebuilt the indexes and tested saving a

new record which updated correctly.  Immediately after the save I checked the

!TABLE 0 record and the data was there.  I thought the problem was 

resolved until today when the creation of some new records did not 

update.  I saved another test record and nothing was written to the 

!TABLE 0 record.

   One thing that has caught my attention this time,  however, is the

!TABLE *INDEXES record.  I'm assuming the purpose of this record is

to store the fields indexed on a specific table.  On the tables where the

indexing is updating correctly the record looks like this:



FIELD1²FIELD2²FIELD3



But, on the table with the indexing problem the same record looks like

this:



1**²FIELD1²FIELD2²FIELD3²FIELD4²FIELD5



What is the 1**?  And, does the key field need to be listed first?



Thank you all for your earlier assistance and any further help you can 

can provide will be greatly appreciated as well.
</QUOTE>
----

=== At 08 OCT 1998 09:59PM Larry Wilson wrote:  ===

<QUOTE>I would run a program to check all dictionary and table Ids to make sure they contain no delimiters.  Have a character GT CHAR(240) can cause just the type if *INDEXES problem you're seeing.  Also, check the data/dict files for a null ID existing; even a null ID can have a 1 in field 6 if it's in the DICT, thus causing that to index.



Send your email address, and I'll send my validator programs.

Larry Wilson

tardis@earthlink.net

http://members.tripod.com/rehabsw     (NEW homepage, Frontpage exten.)

</QUOTE>

----

=== At 12 OCT 1998 02:03PM Aaron Kaplan wrote:  ===

<QUOTE>The **1 is some sort of self-refercing relational used for updating symbolic indexes.  Not sure what it's doing there, but I'll bet you have some errant data in a dictonary record.



akaplan@sprezzatura.com

[url=http://www.sprezzatura.com" ]Sprezzatura, Inc.[/url]

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

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

</QUOTE>


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