Need help with an .OCX error in my VB6 application

Hi Experts,
I added a new feature to my VB6 application.  I have installed this version of the application on a small number of computers for testing.  Some of the users have gotten an error saying that their machines are missing mscomct2.ocx.  I have solved this problem by manually copying the .ocx from my machine to theirs.  If i reference the mscomct2.ocx in my project, will that prevent users from getting this error?

Thanks in advance,
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If you want to distribute your application, you can use the Package and Deployment wizard to create an installation package that will include all the required files.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Éric MoreauSenior .Net ConsultantCommented:
>>If i reference the mscomct2.ocx in my project, will that prevent users from getting this error?

and it also need to be part of setup package
mainrotorAuthor Commented:
So, simply referencing the .OCX and creating an executable will not resolve the problem?
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Éric MoreauSenior .Net ConsultantCommented:
no because it also need to be installed (copied and registered) on any computer using your application
The OCX  will have been added as a component to your project. No other reference is needed. However, it will have to be distributed to systems that do not have it. It will need registering as well, e.g:

regsvr32 "C:\Windows\SysWow64\MSCOMCT2.OCX"

Your path may differ.

The setup in the PDW package will do that.
Martin LissOlder than dirtCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.