Yep!
I changed the execution-order/code-location and the problem when
away. This was a really strange bug. I don't think I will forget the
solution quickly.
Thanks for your help.
Tony
On Aug 7, 2006, at 4:13 PM, Roger Clary wrote:
On Aug 7, 2006, at 5:55 PM, Tony Cerrato wrote:
I am seeing a bug that only occurs in a compiled app. In fact, it
appears to only occur in an app compiled for Windows. I am using
RB 2006 r3.
In order to find the source of the problem I began to insert
MsgBox statements in various places so as to report to me where in
the code something was not right. The weird thing is... I found
the present of the MsgBox itself (at just the right location in
code) solved the problem! It would appear that the MsgBox was
forcing RB to "flush" memory or to do something that would not
normally be done at that point in execution.
I have since played around with a Refresh statement, this had no
effect. I don't believe that my issue is a screen-redraw issue
since the "magic" MsgBox is not being placed in a GUI class.
The description of your problem sounds like situations I often find
(particularly on Windows) where the order of events can cause a
crash. Usually if I put something in a short period timer to happen
later after other events have processed, the bug will go away. See
if there's something (a window close, a method execution) which can
be delayed at the point where the bug is occurring. That may be why
the msgBox seemed to solve the problem.
Roger M. Clary
Class One Software
http://www.classonesoftware.com
[EMAIL PROTECTED]
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
