Stored procedures - unpredictable or what ?!

Hi all, Firstly I'd like to say that I like SP's. Love them, in fact. But only when they work. If I write an SP and it doesn't work, that's OK - it's then down to a mistake in my progging, and is usually fixable after a quick R of TFM, cup of caffeine, phone call/email to our IT people. What I really hate is an SP that works one day, crashes out with an error message the next day, and causes the whole system to core dump the next. (OK, the last one hasn't happened yet, but it's only a matter of time!). The problems always occur with system statements, and tend to throw up spurious errors such as -1, -10, -11, and even a -103 - scary. (I won't waste bandwidth by telling you what these errors are - they are all totally irrelevant to what the SP is trying to do, and as I said, they don't seem to happen all the time. 'finderr' will give you the error message). Questions: 1) Is anyone else out there having these problems ? 2) Has anyone found a solution ? 3) Is it time to go home yet ? 4) Why can't my organisation employ a professional Informix type person ? Yours in anguish, Richard. NB I'm using Online 7.10.UD1 with dbaccess I've got a sneaking suspicion that our internet connection is playing up. If you reply to the list, and the posting bounces back, please don't just curse me. After you've cursed me, could you resend the posting to: r.thomas@csl.gov.uk TIA