Can I use MSWINSCK.OCX without registering it on every deployment PC?

I am upgrading a large program from XP to Win7. It includes a small VB .exe that I have recompiled in VB6 to run on Win7. When I run it on a target machine, I get:

Component 'MSWINSCK.OCX' or one of its dependencies not correctly registered: a file is missing or invalid

There are dozens of notes on the internet about copying the .ocx file to the system folder and registering with regsvr32.  I cannot do this for hundreds of target Win7 machines - especially in administrator mode.

Is there any way to make this active X control self contained? I need the .exe and related files deployed (copied) to a single folder as it was before. Is there any way to do that?
LynnFogwellAsked:
Who is Participating?
 
eemitConnect With a Mentor Commented:
Don't use MSWINSCK.OCX, use Winsock API.
Using Winsock API enables you to have more control.
Also, you never copy Winsock DLLs from one system to another.
Use Winsock version two (ws2_32.dll).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.