>
> Anyway I've got to go away for ten days so I've given my client an
> action
> plan and I'll keep my fingers crossed. I'll take this up again when I
> return.
> Alan

I see I'm not the only one with this error now.
I am swallowing it for the moment because it does not appear to be
destructive but I would like to hear from anyone else with this issue to try
to get to what causes it.

There appears to be no pattern to my incedents other than to say again that
it is when a grid is being re-drawn on a query with a read only read
committed transaction. The query is of a view which calls a
substring(blobfield from 0 for 250). The SQL monitor shows only varchars
coming OTW (and not a blob then being requested separately) so the error
appears to be returned by the server itself when the row is refreshed on a
blob which is out of date.

Alan