Yep, the display and the printing stop until the user move the mouse. I've seen this scenario with DOEVENTS, but the report doesn't call any function with a DOEVENTS in it.

I must admit that the report is pretty complex, calling 2 externals functions repetively, having multiples tables with relations and a lots of fields, but it work OK 98% of the time. The other 2%, the user has to move the mouse, but it will print correctly after that.

I'm stomp. I've suspected timers, but I'm pretty sure that no timer are active at that time (it's not me how wrote this application, BTW).

I'm using VFP 6.0 SP3 and the VFP report writer.

---

>..Move the mouse?
>
>I've seen the same thing happen with Crystal Reports. The simplest solution is to just wiggle the mouse when it stops. I've never been patient enough to see if the report has actually stopped gathering or if the display is just not updating. (especially since i'm usually looking at it over a pcAnywhere connection)
>
>No doubt, the cure is worse than the cold.