Thank you, Ann,
I almost started getting mad about it :-)

>>I get an "internal error" with my procedure that has a BLOB parameter:
>>Calling P_TRANS_TEST in the following code shows the result.
>
> Yes, it's a bug, but the parameter you're passing isn't a blob, it's a
> string. In most cases, we handle conversion from a string to a blob
> nicely, but in this case, not. If your procedure actually expects
> strings as input, then declare it with string parameters and you'll work
> around the problem.

Hm, yes, I expect strings to be the input, that's, afaik, allowed,
concerning the declaration of the blob... ok, it's a bug. The best strategy
around it, is to declare my parameter to be a string, ins't it? Or am I
able to notify my input being a blob of the appropriate type (if so, how?)?

Again, thank you for your answer.

Best wishes,
--
Thomas.Beckmann@...
Martens & Prahl EDV, Wielandstr. 14c, 23558 Lübeck
Telefon 0451-39904-525 • Telefax -520/-559