OCX Dependency

Hi All,
We have some VB6 applications developed. And the executables are generally distributed to users who use the application for various purposes. All applications are Window based apps developed using MS Visual Studio 6 Enterprise Edition.
But users frequently complain of problems running the EXEs. We usually send the exe and the dependent OCX files through a mail (we do not go the Setup Package route due to max size limitations of our email). Users are guided to register the OCXs first and then run the EXEs. But most users complain that OCX registration fails frequently. Also users who were able to successfully run the EXEs fail to do so at a later point since the OCXs got corrupt and they are required to re-register the OCXs bringing them back to square one. We are absolutely in the dark as to why the OCX registration succeeds sometimes and fails for most of the times.
So can anyone point me the common reasons for OCX Registration failure? And someone suggested us to migrate to .NET to end this problem once for all. Is it a good idea to migrate the existing code to avoid the OCX dependency?

Welcome to the Forums.

You will still have dependancy in .NET as it depends on the .NET Framework. Could be failing on registration due to user permission issues. Why not create an internet setup package for them to download. Then the registration can be handled automatically.

Hi, Thanks for the response.
By 'Internet Setup Package' you mean the package built using the Package and Deployment Wizard? Can you please explain the process of creating such a package?

Choose the first option which is to package.

Moved

Those thing happen if you shortcut thed installation process.