Runaway Print Spooler in XP

[parsman]

We have a large PB app that contains several complex reports. The app was originally written in PB5 and converted three years ago to PB6.5 In NT 4.0 'til last month when we went to XP. After going to XP, two of the reports (out of 6 total) can now take as much as 20 minutes before being completed and displayed on the window. These reports would require around 30 seconds in the NT environment. We found that the XP Print Spooler was causing the app to hang. Birds are nesting on the desktops

The reports that take so much time are "built" in script using SetItem instructions. Those SetItem seem to fire the spooler even though it's way before the user can choose to print. The good reports are produced entirely through the SQL Select in the datawindow without manipulating individual columns.

We recompiled the app using PB8 without effect. Has anyone else seen this? Any ideas on why the diff between XP and NT? Any ideas on solving the problem?

 

[vulcanjena]

I don't think there is any problem regarding the OS.
Make sure you installed correct PB runtime dlls along with any OCX (if any)that are used in any reports.