I don't think so. This seems to be a problem related to the BLOB ID
changing between one transaction and the next. Not sure how they could
fix that in Firebird without a change in the design of BLOB IDs.


Thomas Steinmaurer wrote:

> Hello Stephen,
>
>
>> Found a solution. I changed the stored procedure to return a VARCHAR
>> rather than a blob and used the SUBSTRING to cast the BLOB to a VARCHAR.
>>
>
> There was also one bug fix related to BLOB not found and PSQL in
> Firebird 2.0. Can't say for sure that an upgrade to 2.0 would cure the
> problem in your scenario.
>
>
>
>

[Non-text portions of this message have been removed]