Problem in Using the Custom made OCX
-
Hello all, I have made an ocx . It includes the Winsock and the Timer controls . But the problem is that when I try to use the ocx in the application on some other computer the application gives error about the using the correct version of the OCX. Now when I place the ".ctl" file along with the ocx , it works fine . Now It is really annoying as i have to install complete visual basic setup on the client PC so that ".ctl" file works with ocx as app does not run only on vb runtime. Please suggest the solution.
-
Hello all, I have made an ocx . It includes the Winsock and the Timer controls . But the problem is that when I try to use the ocx in the application on some other computer the application gives error about the using the correct version of the OCX. Now when I place the ".ctl" file along with the ocx , it works fine . Now It is really annoying as i have to install complete visual basic setup on the client PC so that ".ctl" file works with ocx as app does not run only on vb runtime. Please suggest the solution.
I remember when using VB6 it had a thing about increasing the version number at the slightest opportunity. Maybe this is the same problem? I seem to remember an option in the object to stick with a particular version, pointing the settings at a Version Compatible Component to make this happen comes to mind.