>One other item you might be able to give me an opinion on. I found it easier to have my setup program to call their INSTALL.EXE to install the Amyuni Printer Driver on my end user's machine. Since they have released this version 2.10, it has been updated at least 3 times (last time this past Saturday). I was informed by their support tech's that I need to actually un-install the prior version with INSTALL -U, then run their INSTALL.EXE again. However, all the .DLL, etc. files it installs are the same as far as I can see. Having to run this INSTALL -U on 2,000 desktops has already become an 'issue' that is a little difficult. How do you deal with this? I guess what I am asking you is this: I can see where the 'safest' way to make sure the compter has a clean install is to unstall it first, then re-install it - but I wish it were the not necessary.
>
>Mel Cummings

Yes - I think there's a dll or two that need to be unregistered during the uninstall process or else you'll have troubles.

If you're an in-house shop with 2,000 desktops, I'd recommend using a workstation admin utility like Novell ZenWorks or MS SMS. They both work on windows clients and allow you to install and un-install stuff. With a little care and planning, they can make your job MUCH easier. I was working with ZenWorks when I was running a network with around 100 users (I've had no direct experience with SMS).

Alternatively, I don't know if your users are using the PDF driver outside of your application, but if they do NOT I would consider switching to the 'developer' version of the Amyuni product. I like it because it involves distributing only a few dll's (and registering one). You can then create and destroy new PDF drivers from your app as you need them. This means you don't have to worry about a user or administrator deleting or renaming the printer driver on you. I like using this with my apps, and controlling it as an ActiveX object. VERY flexible!

HTH