5 replies
by john.a.wills Accepted solution
by tony hopkinson Accepted solution
of Try Catch(Exception) isn't picking it up. some piece of code much further in is putting up the error and then swallowing the exception so your code never sees it.
Not the first time I've seen that sort of thing. If that's what it's doing the only thing you can do is write your own validation and cease to rely on the feeble minded drivel that's dealing with it now.
If it's exception types put a catch all round your code and see what comes, an OLEException is a regular candidate for this sort of thing.
by john.a.wills Accepted solution
by tony hopkinson Accepted solution
I had a choice on feeble minded either. :(
I ended up with no option but to try and test for this particular instance and avoid the excpetion being raised. Course where there's one issue, there are always six more waiting to leap out of the woodwork...
Is it just this instance or are any PL/SQL exceptions being swallowed?
by john.a.wills Accepted solution
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending