I checked the call stack and there are no TRY/CATCH blocks around any of the
calling code. I also do not have JIT debugging enabled in the IDE.
More information:
Prior to opening the window with the datawindow causing the problem we call
a function which launches another thread with sharedobjectregister and POSTs
a function. If I comment that function out the systemerror event does get
called, but only when I do something on the window such as click a button,
or the datawindow control or something. It does not trigger immediately
(from the IDE anyway, haven't tried building an exe). Very strange.
We are on PB 10.2 build 7516.
Any insight?
(Hi Roland!!)
Thanks,
Jay
Are you accidently triggering a runtime error within your system error
event?
Does your system error event depend on the contents of any global
variables that may no longer be valid?
Try adding a simple messagebox call to the start of the event to see
if it really happens.
Do you have any code in the DBError or Error event of the DW Control or
DS? If so, that is executed 1st before the System Error. In these events,
you can suppress the SystemError from being called. Just a guess here.
--
Regards ... Chris
ISUG - NA RUG Director
http://chrispollach.pbdjmagazine.com
"Jay Williams" <jwi...@cvps.com> wrote in message
news:48b592c8$1@forums-1-dub...
"Jeremy Lakeman" <jeremy....@gmail.com> wrote in message
news:cc539711-63e0-4f6e...@25g2000hsx.googlegroups.com...
I am using PB8, PB9 and PB10 and the PB10 IDE is definitely more likely to
abort for no apparent reason.
"Jay Williams" <jwi...@cvps.com> wrote in message
news:48b592c8$1@forums-1-dub...
The DW control where I am getting the abort is on a response window opened
from a main window.
I imagine I could fix this one problem area by wrapping it in a TRY/CATCH
block or checking the row, but we have seen other places in the app where it
is just closing without error, but we cannot recreate those.
"Chris Pollach" <cpol...@travel-net.com> wrote in message
news:48b692d6$1@forums-1-dub...