Most likely StrToInt is throwing an exception when you pass it a string that
does not contain a valid number. If you are running the program in the IDE
be sure to set "break on exceptions."
-Mike
This isn't from my code. I have a vague idea of where the +OK comes from,
but I haven't been able to track it down. The error occurs infrequently, in
a program that runs continuously, so for that reason and others I can't
easily put in breakpoints and just debug it.
(1) Could this message come from an IntToStr? I would think that almost
any pattern inside an integer, even if overwritten, would still look like an
integer.
(2) If not an IntToStr, then is there any Borland function that would
produce this message?
(3) If not from a Borland function, should I assume it's from a package
I'm using?
Thanks for any help!
Glenn Polin
Yes, StrToInt creates an exception. If your code does not handle the
exception the default exception handler throws up a dialog box just like
what you've described.
-Mike
Glenn
"Michael Williams" <mi...@remove.aps-soft.com> wrote in message
news:3ad3211b_2@dnews...
Assuming that StrToInt is throwing this exception and that you're running
under the IDE debugger, several things are possible here:
1) You have "Stop on Delphi exceptions" turned off in the debugger options.
2) You have EConvertError in your list of Delphi exceptions to ignore.
3) The exception is being handled by the procedure that called StrToInt, and
throwing up a dialog box in the except block (though even this would cause a
break under the debugger if you have "Stop on Delphi exceptions" checked).
Your best bet is to set a breakpoint somewhere before the error, and step
into everything (F7) until the dialog box appears. Then at least you might
narrow it down to a given package or unit.
Michael