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 07 DEC 1999 07:01:22PM Matt Crozier wrote:

Does anyone know what the third subvalue in the !table record of a

!table file is used for? I thought it was always null but I've come across some instances where it is a '*'. This seems to have occurred when the internal volume labels have been mixed up/renamed/whatever and a second line (vm'd) has appeared in the !table record.

Thanks,

Matt.


At 08 DEC 1999 10:55AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:

If I remember correctly, it was used to hold some sort of information about irregular fields ( not data or symbolics) but I don't believe any of the information was actually used.

[email protected]

Sprezzatura Group

[/i]World leaders in all things RevSoft and obscure ARev stuff[/i]

www.sprezzatura.com_zz.jpg


At 08 DEC 1999 01:00PM Matt Crozier wrote:

Thanks Aaron, I can understand why those extra lines would be irregular. So I can ignore the '*' when fixed them up.

Matt.


At 08 DEC 1999 02:01PM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:

If it were me, I'd remove the extra lines. Problem with indexing is there are lots of little goodies that were added into the code, but never finished, for various reasons. Computational, symbolic, node size manipulation, sorting, justification and the like. Keeping this there might trigger a section of the code that was never debugged and could have "interesting consequences".

[email protected]

Sprezzatura Group

[/i]World leaders in all things RevSoft and !files[/i]

www.sprezzatura.com_zz.jpg


At 08 DEC 1999 06:19PM Matt Crozier wrote:

Wow! that's good to know. All this happened because the DBT became out of synch with the volume labels so when copying across DICT items during RDKINSTALL, another line was added in the !table record for the other media name. All the other index definition stuff is OK though, so I'm just copying the index specs from one line to the proper one and removing the bogus lines, and rebuilding indexes where necessary.

Thanks for your help.

Matt.

View this thread on the forum...

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