Sergey, this has been reported by both myself and our Swedish office, probably, half a dozen times to Microsoft and Ken Levy has been asked to intervene. There has not been a single response except for Ken indicating that Tech Support is not his area and that he would pass it on to the correct people. The correct people have not responded.

VFP 7.0's Report Writer is fatally flawed and nothing is being done to correct the problem. Our research indicates that it is related to memory since the rate of GPF's and C5's goes down immediately after a reboot and then climbs to the point where the Preview function is a total embarassment. The problem occurs under WXP, W2K. It does not happen with VFP6.

In San Diego at the VFP Conference, Ken indicated that Microsoft wanted to drive the acceptance of VFP forward - not fixing the most in-your-face bug, one that is easily reproducible and has been the subject of complaints since the launch of VFP 7 (it is not even fixed in SP1) is no way to drive the acceptability of VFP. Customers who cannot print their reports are not happy!

This bug deserves the highest priority right now.

If Microsoft wants to telephone me, I am their service 24 hours a day on +1 973 394 0497. I will be happy to supply any additional information they require.