Hi Ed.,

>These two errors are equivalent in their layer, but they error being trapped is slightly different (under one, it's an error addressing memory not belonging to the process, in the other, a BOUNDS check is out of range); it's curious that they occur at the same virtual address under two different operating systems that allocate memory in different ways. Is the address really the same, and repeats consistently at the same virtual memory address under both operating systems?

According to the customer, yes. I agree that that sounds a bit strange.

>
>I have no idea why you're getting this, since it looks quite legal and valid; I'm a fan of simplification, though, and in this case, you could simplify your WHERE clause. Assuming that grn_jobnumber is a character field, the logical condition:
>
>! EMPTY(ALLTRIM(grn.grn_jobnumber))
>
>is exactly identical to:
>
>! EMPTY(grn.grn_jobnumber)
>

I'll make that change. I don't know how got into the habit, for I always seem to deploy ALLTRIM() when using EMPTY().

Like you, I was thinking of the printer drivers, so that's worth looking at further.

Thanks for your prompt reply.

Matt.