Arev Version 2.12 ??upgrade problems $insert (AREV Specific)
At 22 NOV 2004 08:07:04PM Les Leibbrandt wrote:
I am trying to access the dictionary for a file and get the message "rebuilding control records in the dict.congregation file' followed by "the $insert file 'utility.progs' is not available press any key to continue" . The programs have been ported over from ver 1.16 and had been running but now under 2.12 get this message - this file also has some relational indexes on it. The file utility.progs
has not been an available file for some time and could be ver 1.16 related.
I have removed the indices manually and need to get into the dictionary to complete the final process of the index removal. The problem with the message "the $insert file 'utility.progs' is not
available press any key to continue" cropped up in the last 80s early 90s and there was a quick work around this problem using a portion from the verbs files. However due to aging and poor
memory recall I have not been able to find the fix or the work around. Any ideas greatly appreciated.
At 23 NOV 2004 02:07AM [email protected] wrote:
When you change AREV versions, AREV checks the version of the dictionary code and if it is outside certain levels it attempts to recompile the dictionaries before allowing access to the file.
Your system is trying to do this and failing because it cannot find the needed insert.
For now comment out these inserts in the dictionary formulae.
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 23 NOV 2004 07:18PM Les Leibbrandt wrote:
It won't let me access the dictionary items so that I can elimiate the $insert portion of the dictionary
At 24 NOV 2004 01:52AM [email protected] wrote:
Interesting - well the EASIEST way from a power user perspective would be to edit the REVMEDIA map, create a synonym entry without DICT.MFS then use this to do the editing removing the synonym after use. The other easy way would be to write a program that opened the dictionary and remove the dict.mfs from the file handle then did the necessary updates. You could also play with a SET-FILE DATA to file DICT and see where this took you.
The Sprezzatura Group Web Site
World Leaders in all things RevSoft
At 24 NOV 2004 10:34PM Jonathan Bird wrote:
Wouldn't it be better to issue a SETFILE command at system startup? Something like:
SETFILE REVBOOT SYSPROG SYSINCLUDE UTILITY.PROGS
j
At 26 NOV 2004 03:17AM [email protected] wrote:
If that works - almost undoubtedly! ;)
The Sprezzatura Group Web Site
World Leaders in all things RevSoft