Getting very fed up trying to implement Winsock. A few environment notes before I begin. My home office system is a Vista 64-bit OS, development machine at client site is XP-64bit OS and client workstations are Win7 or XP-32bit. Working in Access 2003.
Working at home, I made a form with a Winsock (MSWinsck.ocx) object and successfully transmitted data to a listening server.
At the client site with my form from home, the Winsock object was not recognized. So I deleted the object from my form and then registered MSWinsck.ocx. But when I tried to add the Winsock object to the form again, Access said "(Project Name) does not support that Active/X control".
Research indicated a Microsoft hacker defense called Killbit caused that. After downloading a new MSWinsck.ocx and registering it, I get a new error message when I try to add the Winsock object to a form. The message is "You don't have the license required to use this ActiveX control."
MS says to recompile the project to make this problem go away, which didn't change anything for me. But their target audience when they said that was VB6 developers, and I'm in VBA. And I sort of thought they were talking about recompiling the ActiveX control, not the project using the control
Anyone know how to get around this? Here's a link to the Microsoft blog where I got my fix procedure from.
http://blogs.msdn.com/b/vsod/archive/2009/06/05/visual-basic-6-controls-stop-working-after-security-advisory-960715.aspx
Thanks,
Jim