Benjamin:
Any
time R:Base crashes it shows a problem with RBG65.exe (unless the computer
freezes). I would carefully follows the code, particularly the lines before
the point where your application crashes (use TRACE), looking at the variables
and checking whether they have the correct type and /or value; many times
variables are redefined and create problems. Most of the time, you will find
that there is a problem with your code and or variables, you can also use
R:Style to check your code.
I
recently run into a problem caused by a Blob loaded with the initial
application screen that caused the system to crash way down the code. Mike
Willochel at RBTI finally figure this out and he was able to come up with workaround to
this particular problem. If after all you efforts you still cannot find the
problem, give tech. support a call, I have found then to be very responsive
and helpful.
Javier
Valencia, PE
President
Valencia
Technology Group, L.L.C.
14315 S.
Twilight Ln., Suite #14
Olathe,
KS 66062-4571
(913)829-0888
(913)649-2904
FAX
-----Original
Message-----
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Strickland
Sent: Sunday, December 22, 2002 1:38
PM
To: RBASE-L Mailing
List
Subject: [RBASE-L] -
System Crashing when printing reports
Has
anyone had the problem printing reports and what is happening is when I
change to another [where] condition or change reports in my code, the
program crashes showing problems with the RB65.exe file? What could be
possibly wrong with the system or code? I am using the latest version of
Rbase, 6.5++ including the latest patch.
Benjamin
Strickland
