Interestingly, I traced rbase.dat using [F10] to single step with
vErrVar and vErrSave in the side window, and the error changed
immediately and only on the CONNECT line. I also did R>CONNECT and no
error, then TRACE rbase.dat and got the error message again. I have
followed Razzak's suggestion, and am investigating further.
Thanks for the thought.
Albert
On 4/8/2015 12:01 PM, Javier Valencia wrote:
Albert,
Have you tried TRACEing the startup file? You can go line by line and see
exactly where the message pops up.
Keep in mind that when you start the TRACE the last error found on the previous
trace always pops up...at least it does for me; I believe I submitted this to
RBTI a while back but I am not really sure, just a minor annoyance.
Javier,
Javier Valencia, PE
O: 913-829-0888
H: 913-397-9605
C: 913-915-3137
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Albert Berry
Sent: Wednesday, April 08, 2015 10:13 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Strange error
In the last short while, a client is getting this message when attempting to
connect to a database. I have verified it on my copy of the database.
Does anyone have any idea what would cause it? I have a trap for error on
connection - the part of the code file that does this to us is below.
<WARNING> Output has been truncated. (2642)
Code snippet with database name hidden for privacy.
DISCONNECT
SET ERROR VAR vErrVar
SET VAR vErrSave INTEGER
DISCONNECT
SET MULTI ON
CONNECT DBName
SET VAR vErrSave = .vErrVar
SHOW ERROR vErrSave
RETURN
Albert the confused
--
A democracy ..." can only exist until the majority discovers it can vote itself
largess out of the public treasury."
Attributed to Alexander Fraser Tytler 1747-1813
