[[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]]


==== More on error 27.4 (Reporter Specific) ====
=== At 01 MAY 2001 07:08:56PM Bob Silverstein wrote: ===
 
{{tag>"Reporter Specific"}}
 
<QUOTE>
I have been getting this error message from time to time.  Based upon advice posted here, I changed all my dictionary entries for F data types from {xxxx} to @record.  I am still using some symbolics  While this has reduced greatly the error, I would like to a step further.



When saving a record in the first screen, an Rbasic routine does various processing and then passes a record to a second screen.  Could I put a RESET statement into that routine?  Can I see how many variables are in the stack by putting a DEBUG in that routine?



Thanks for the help.
</QUOTE>
----

=== At 03 MAY 2001 08:37AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:  ===

<QUOTE>You can put a debug in to examine the variables used. Bear in mind the answer given will be slightly misleading [i]vis a vis[/i] memory as the debugger will do a garbagecollect/flush before displaying the ! prompt.



To see used varables type # at the debugger (!) prompt and press return.



If this is really such a big issue when leaving one screen for another it might be symptomatic of a wider design problem - however you might like to experiment with CHAINing the next porogram to srop everything else off the stack.



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

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

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

</QUOTE>


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