Killbit killed my VBA Winsck object

[jimatqsi]

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

[NeoPa]

I'll keep an eye on this Jim, but I can't help here I'm afraid :(

[jimatqsi]

I have a copy of MS VB 2005 Express, so I installed that. It magically made my problem go away. But, this nagging fear says it could show up again with the next udpate from MS.

Jim

[Denburt]

I have a copy of MS VB 2005 Express, so I installed that. It magically made my problem go away. But, this nagging fear says it could show up again with the next udpate from MS.

Jim

I did a little digging and found out that you can remove the killbit for the winsock control although I wouldn't recommend it. From what I read upgrading to the latest winsock control should resolve the issue.
Just as an FYI here is the registry key I found that should kill the Killbit for this control:
HKEY_LOCAL_MACH INE\SOFTWARE\Mi crosoft\Interne t Explorer\Active X Compatibility\{ 248DD896-BB45-11CF-9ABC-0080C7E7B78D}
"Compatibil ity Flags"=dword:00 000000

[jimatqsi]

Wow, thanks very much. I might have to use that. The darned thing was working fine one day, after I installed VB, and then the next day it's broken again.

It just does not make the connection. I'm going to delete the Winsock object from the form and make a new one, maybe that will do something. But even if that works, or some other fix works, I don't have any confidence the use of that object is safe.

I'd much rather use the API. I'm wondering where I can find a guide to write my own Winsock control.

Thanks very much,
Jim

[Denburt]

Wow, thanks very much. I might have to use that. The darned thing was working fine one day, after I installed VB, and then the next day it's broken again.

It just does not make the connection. I'm going to delete the Winsock object from the form and make a new one, maybe that will do something. But even if that works, or some other fix works, I don't have any confidence the use of that object is safe.

I'd much rather use the API. I'm wondering where I can find a guide to write my own Winsock control.

Thanks very much,
Jim

I have done some looking and there is a windows update that can break the winsock control and another that fixes it. Forgive me for not providing more info, this is an FYI.

I have also looked a little about using the API and although it can be done I have not found enough info to provide you with any coding that can be of help. If I do find anything worth mentioning I will be back and if you would please post any relevant information that may help other posters we would all thank you.