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 01 MAY 2001 07:08:56PM Bob Silverstein wrote:

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.


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

You can put a debug in to examine the variables used. Bear in mind the answer given will be slightly misleading vis a vis 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.

The Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...

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