Hi George

Thanks for the continued response. All of our reports are from a SQL-generated cursor. It is rare that we do any in-line processing - we do pass on header stuff and so on but nothing major. However, many of the reports are large and therefore, depending on the way in which Preview handles them, memory hungry.

Perhaps the issue I have with this is that I cannot find anywhere, an acknowledgement that there is any problem with VFPRW and memory. Perhaps I have missed something. The least I would expect is a note on the Known Issues page saying "We are doing something".

Anyway, we are ditching VFP Report Writer and moving to Crystal. We cannot have someone else's product giving the impression that ours has problems and we are not fixing them. The rewrite will be worth it for the stability.

Now, I wonder if I can get them to remove the VFPRW elements from the runtime to make it smaller? <g>

Thanks again

Paul