I have this problem all too often. Most often the Win.ini has become corrupt so I just replace the win.ini with a known good backup(which I now make at the beginning of every program that deals with printing). If you don't have a backup, 99% of the time if you reset the default printer from the control panel, by right-clicking on a printer and choosing "Set As Default", this will reset everything to the way it should be. The other 1% involves uninstalling and reinstalling the drivers. Good luck.

Paul



>Hi everybody,
>
>A client of mine is getting the above error when they try to print to a printer which is not their default printer.
>
>It looks like the situation describe in mskb#Q253884 but the strange thing is it started this morning.
>
>They are using many printers most of them being HP, the newest one being added 5 weeks ago being a HP 41000.
>
>This morning I upgrade their accounting software which is programmed with VFP6.0 SP?. From the upgrade CD, there is an option to reinstall runtime. I had to do the "runtime" installation for each workstation because at the same time it install Chrystal Reports (version 7.0) runtime which is now use with the accounting software. I know the installation installed a few .dll and other ??? file, it might also have change or upgrade existing files I don't know exactly.
>
>Obviously the installation created a conflicting situation but where? Does anybody has an ideas where to search for?
>
>
>We already changed the HP4100 driver and a HP2200 driver to a driver available from microsoft (Deskjet 4). And we will upgrade their VFP runtime to the latest SP tomorrow (they have SP3 right now)
>
>
>Any ideas as to wath else we should try and in which orders to try them would be appreciate.
>
>Thanks,
>
>Diane Robitaille eng.
>GCIMicro