Cannot create ActiveX for Internet Explorer using the Application Setup Wizard

Internet Explorer reports unknown type .VBD for Active Document
I have carefully been though MS article 167380 but that doesn't help.
Basically the activeX works beautifully on the development pc but when I put the package (from the Application Setup Wizard) on a test web server and access the page from a computer other than the development PC, that computer then doesn't know what to do with the .vbd file and asks to save it. (ok - yes first of all it asks to install the .cab file then it gives the ask to save question)

All test computers are running IE 6 , some Xp sp2, one win 98. All fail.
I have added the test webserver site to the local internet zone and set its security to low.

I have googled, groups and web, but all things I have found and tried make no difference. I just think IE no longer knows what to do with a .VBD file. Ahh yes the .vbd file was created using VB5.
I really like using this method to convert my apps to intranet available web pages as it can be done with minimal changes.
Thanks for any ideas....

Moved to Application Deployement

Internet Explorer reports unknown type .VBD for Active Document

How To Test Your ActiveX Documents (.VBD)

Thanks dilettante,

But had you taken the slightest moment to read my post you would have noticed that :
1. I had already read and tried the first link you sent and
2. It was working on the development machine therefore the second link doesn't apply ( and yes I had read it first and yes it test perfectly in debug mode as mentioned in the original post.)

Thanks for your non-idea.

Webgurupc

I did actually solve this and it works beautifully.There are two options. All of the original programs related to missing or out of date DLLs.

1. Create your program so that it does not use any add ins or components. This is my preferance as it will run on anything and does not require any administrator privledges to install.
It is not so hard to do. I have created my own report writer, my own msgrid equivilent, etc. And once done it given has to be done again and can be re-used.

2. This one really only applies where you know who you project will be rolled out to. But it is to create a new project and toss every component into it that you use or are ever likely to use in your programming life. Create an installer for this project and call it Applet Installer. (This will require admin privledges to install). Once this dummy program is installed on the users computer any vb project will run without the need of another admin install (unless of course it uses custom or updated componetents)

----
please let me know if anyone out there still uses this dead art.