Brandon,

The problem is that it cannot be reproduced. It is RANDOM (i.e. not reproducible) on machines with > 1 GB ram - happens every tenth(?) time. I am not convinced that it is a report problem specifically but a random memory problem that the user obviously sees when they see the "report" printed. The app allows canceling the transaction and doing it again - the second time its always OK.

From the behavior it seems like a VFP8/9? memory bug. Anyway, I stated how to avoid it. If it wasn't a memory bug why would restricting Fox memory usage to below 1 GB solve it?

>Have you been able to write a .PRG to reproduce this behavior or is it limited to reports? Can you provide testcode to reproduce? I would very much like to test on my machines. I've got a Vista ultimate machine with 4GB to test with.
>
>
>Brandon