RTP57 and RPT18 B114 Error (AREV Specific)
At 30 NOV 1999 03:24:39PM Josep Cabré Vilagut (Barcelona - Spain) FACOMSA wrote:
We are using AREV ver. 3.12, with Revelation NLM ver. 1.5, in a mixed environment with W95/W98/DOS workstations, under Novell 4.1. We assign Expanded memory (EM allocated 4,194,304) by setting the command line as appropiate.
Sometimes when switching screens (programs in RBASIC) we get a sequence of errors in the screen:
'RTP57' Line 1. B114 Maximum number of variables exceeded.
Line 1 'RTP18? broke because a run time error was encountered.
Press Esc to leave the debugger.
After checking the documentation and the settings of installation we don't see any light. All data base files appear as well dimensioned "good".
This started happenning only recently after 1 year and a half without problems.
Does any one provide any help.
Many thanks in advance.
Josep
At 30 NOV 1999 06:15PM Victor Engel wrote:
This is most likely a coding error of some kind. You are limited to something on the order of 5000 variables. This includes dimensioned variable elements, so DIM X(100) uses 100 variables.
Pay special attention to labeled commons as these are never relinquished during a session.
Also, look for recursive subroutine calls and multiple TCL levels.
At 30 NOV 1999 08:27PM amcauley@sprezzatura.com onmouseover=window.status=why not click here to send me email?;return(true)", [url=http://www.sprezzatura.com" onMouseOver=window.status=Why not click here to visit our web site?';return(true)]Sprezzatura Group[/url] wrote:
See if Aaron's response helps
amcauley@sprezzatura.com
World Leaders in all things RevSoft
At 16 DEC 1999 05:35AM Josep Cabré wrote:
Two weeks now, since applying a dedicated letter, as Aaron suggested, and no more problems so far.
If no new errors detected, no further feedback from our side will be posted, which would mean good news.
Many Thanks for your help
Josep
At 23 JUN 2005 10:34AM Victor Engel wrote:
Looks like Aaron's reply link no longer works. Do you remember what it was? Can I gather from Josep's reply that it was to set up a dedicated drive letter? What if these symptoms apply when a dedicated drive letter IS being used?
Victor