---
Well, the app takes care, of course, to call the specific printer, depending on the OS used. For instance, there are differences when using SET PRINTER to NAME under XP or Win98 ( for XP i have to use \\ notation ). Anyway, this is taken care of.
---

I would expect that the differences in how you call the printer are taken care of by your app, Jaime. But this still doesn't answer my question: assuming that a printer by the name of SharedFax is the one you think it is, or uses the driver you think it does, is still risky. When your app installs does currently it verify these two things?

Anyway, PITA or no, I like your current solution of a Fax server. FWIW this is a very common solution and makes sense for many reasons:

* -- it is in the tradition of "distributed computing" (precursor to "grid computing", la-de-dah <g>), in which you share a computing burden or load, allocating resources according to the abilities of various resources. This will always be an important thing to figure out, no matter what happens to printer drivers in the future <s>. Whether it seems like an extra step to "move the report" doesn't matter that much in the end, IMHO, considering all you stand to gain by offloading some jobs like this from the "immediate client".

* -- it is a useful, and traditional, resolution when faxes are actually required and actually go out through a phone line! In some scenarios, the appropriate software to send it may be costly, or not all machines have a direct connection to the fax device.

* -- it means that the operation requiring careful configuration (in your case, a specific printer driver with a specific name) isn't required on all client machines, where a user (or at least a less-than-mindful admin user ) might make a change that impacts your app.

You don't really need me to tell you these things, but I wanted to say that I think this is a good conclusion to have come to and will benefit you in the long run.

>L<