Where is the error occuring? in your app or the account software?

It sounds like the runtime files have already been upgraded by the installation of the accounts software.

Do you realise there is probably just 1 set of runtime files so if you have a VFP 6 app on the same machine then it will now be using these files. I think you would be best to re-compile your app with the same version runtime files as used by the accounts software.

If you still get the problems then manully SET PRINTER TO NAME to force the default printer.

HTH
Will

>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