>I have one of those "we changed nothing but now your app is broke" situations. We have a couple of FPW2.6 apps (yes we are upgrading to VFP but time...time...time) which have been running smoothly at over 50 client sites. Within the last 2 weeks, we have had 3 sites begin receiving spool32 errors and system lock-ups when printing large documents. They all claim that they did nothing and installed no new software or upgrades. They were able to print these reports before with no problem.
>
>At one (the closest) site, I changed the printer setting from print to spool to print directly to printer and the problem seemed to disappear for a short while. Now IT'S BACK! - although only intermitently now.
>
>Has anyone else suffered a similar problem, and, even better, know how they fixed it??? I checked the MS support page and they have no listing for spool32 errors and FoxPro.

Having had those problems myself, I discovered it occurred only on systems with HP printers and found some info at http://www.hp.com/cposupport/printers/support_doc/bpd02973.html specifically referring to spool 32 errors. The solution reads in part:
"The Spool 32 errors may be caused by fax or answering machine software programs that have been pre-installed on the computer." and it continues from there with 7 pages of info. Also, I found that changing my lpt port to EPP instead of ECP or EPP/ECP in the cmos helped. Hope this helps or lends some light in addition to what Randy passed on.

Marv