dictionary layout (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]]


==== dictionary layout (AREV Specific) ====
=== At 03 NOV 1997 07:02:20PM Ed Mantz wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
Can anyone tell me what is the dictionary layout for AREV2.11.

I am interested in field 28.

I seem to remember reading somewhere what the layout is but I can't find the info now.  Thanks
</QUOTE>
----

=== At 03 NOV 1997 08:02PM Ed Mantz wrote:  ===

<QUOTE>I have since found that if field 28 is 0 it signifies

that dictionary item is a sysnonym.  A 1 means it is

the master field.  Does the system use this

information in any way?  In trying

to sync up an application running on several systems

I have found the same dicitionary item on 

different systems to have either a null, 0 or 1

in field 28.  Is this field DICT.MFS maintained or

is it changed by some entry screen?



Thanks

</QUOTE>

----

=== At 03 NOV 1997 10:29PM Michael Slack wrote:  ===

<QUOTE>I think you might try the table DICTS.  Something like LISTDICT DICTS or LIST DICT.DICTS might do it for you.

</QUOTE>

----

=== At 09 NOV 1997 11:56AM Aaron Kaplan wrote:  ===

<QUOTE>To answer your original question, the full dictionary information can be found in INCLUDE, DICT.EQUATES.



As for the master fields, these started somewhere in the 2.0 series.  This is a system required and maintained field that indicates with of the many synonyms of the field is the master.



It's primary purpose was for bonding and other data enforcement items.  In LH, you can have one dictionary item, pointing to field 4, defined as MD2.  You can have another dictionary item pointifng to field 4 defined as CUSTOMER.  As you're working with varying data sources, you need to know what is the real information.   That is the purpose of the master field.



In most cases, what it's set to will not matter.  Only in ARev 3.0 is there some slight concern with master fields.  This is related to IDX_SETS.  There must be a key field, part 0 defined as the master, and have a display length 5 chars greater than the largest existing key.  This doesn't affect your 2.12 system though.



If you wish to specify a specific synonym as the master, move all other synonyms to a holding file.  The sole remaining field will be defined as the master.  You can then move back the records from the holding area.







apk@sprezzatura.com

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

[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=43B4E4AEDE3BCBD1852565450000370E|View this thread on the  forum...]]