Sounds liek you really do have a VALUE_ERROR that you're not locating. One
technique might be to write to a package variable the line # of the last
statement executed (sprinkle these assignments liberally). Then in the
exception handler to trap VALUE_ERROR, write out the last known line. This
will help you pinpoint the statement suffering the exception. Or run a debug
on the code from a tool like Platinum or PB. The problem is sporadic because
it only happens for certain data values, so it seems random.
--
- Dan Clamage
http://www.telerama.com/~dclamage
If you haven't crashed the Server,
you haven't been trying hard enough.
RMakanji wrote in message <78o8ds$qq0$1_at_camel18.mindspring.com>...
>I had a hell of a time with a similar problem and it sounds like it might
be
>your problem too if your procedures are using cursors and doing
>inserts,updates,etc. check to see if your procedures allow an uncommited
>transaction to occur before exiting.
>
>If thats the case, when you run the program it starts acting crazy where it
>works then it doesn't and after a few more tries works again.
>
>Hope this helps
>
>
>
>
>
>
Received on Wed Jan 27 1999 - 17:22:26 CST
