How to beat / handle setup....

[sultan]

Hi all
This is somewhat of a constant equation of trouble for me when deploying scripts or and working on setup applications.

Using Package & deployment Wizard:
I have already deployed my applications to 20 end users clients.

This application uses an ActiveX control (ocx). Both package and deployment scripts still exist.

After sometime later I acquired a newer version of this OCX control which is better in perfomance + other benefits.

Now my 20 clients want to make use of this OCX. What would be easiest and quicker way to transfer this ocx to them?

Please be a little descriptive as i am not a full developer and as i am already confused by going into in-depth reading on Package and deployment wizard!

[billrogers]

with this program, do you timely releases to fix bugs and add new features? If so I would wait until they came around. There is another thing, I have seen but never done anything with. Where a vb program is notified when a newer version of itself it available for dl from the internet/copy from the intranet, it will inform the user "Hey there is a newer version of me out there, do you wish to dl and install it?", this is escpically nice, for you never have to worry about distribution media, and having old copies of your setup on media lying around.

[sultan]

Tanks bill
but i want to evoid other tools or other software because i have to learn where to use PDW wizard and also understand about different setup situations and how best to deal with them.