>Make sure the user has service pack 3 for VFP6 on her machine. Try adding another printer definition to her windows setup that used a Microsoft laser printer driver. Only your application needs to print to that particular printer definition. She can use the fancy driver for all of her other apps.
>

Thanks. We followed Ed's advice and installed a series 4 driver and things are copacetic again. We'll use your multiple name trick to use the new printer's native driver for most apps.

Your and Ed's comments have been a big help. Problem solved. Thanks.

>>One of the employees who uses my app just replaced her old laserjet printer with an HP2100, which supports a native mode PCL driver and a backward compatible "5e" PCL driver.
>>
>>Now,with either driver, my app, which is otherwise unchanged, breaks as follows:
>>
>>(1)Run a report - report prints correctly
>>(2)Bring up order entry form - when DE of form attempts Openfiles() system locks up with the famous hourglass appearing and is totally unresponsive even to 3 finger salute and must be restarted with the reset button.
>>
>>Tried both drivers with same results. Problem does not happen if print on another printer in net. Problem only occurs for this user.
>>
>>Another clue is that when the system restarts, the printer coughs up a page with a few hearts printed at the top...kinda like an orphaned printer spool file is being purged. (This only happens when restart occurs after the main problem has occured)
>>
>>Other apps, like Word, print just fine on her new printer.
>>
>>I'm pursuing the hypothesis that something about the new printer driver is combining with VFP to overrun her 32 MB of memory in such a way that crashes rather than an orderly shut down or a 'you need more memory' diagnostic.
>>
>>Any body else have a similar experience for which you discovered a cure?