License

Greetings.
I was loading a project of mine today and discovered that the winsock control was not on the form.
After a short "investigation" I discovered that if I tried to add a winsock control to any project (even a new one) it displayed this error:
LICENSE INFORMATION FOR THIS COMPONENT NOT FOUND.
YOU DO NOT HAVE AN APPROPRIATE LICENSE TO USE THIS FUNCTIONALITY IN THE DESIGN ENVIRONMENT.

What is going on?
This error wasn't being displayed a week ago.

Thank you in advance to all that help or offer advice.
-cl

PS - Can any of you give me a serial number that works.
I wish to download Visual Studio Installer from the Microsoft site and you need a serial number to do so.
I tried mine and it didn't work.
Boy, does Microsoft make me some angry at times.

If it worked a week ago, what changed since then?

Maybe you installed something that overwrote the old control and the new version requires a new licence.

On my system, the control is
mswinsck.ocx 108,336 bytes 6/24/98

Check the path of your winsock component to be sure it's pointing to the copy you think it should.

Good luck!

"I have a plan so cunning you could put a tail on it and call it a weasel!" - Edmund Blackadder

Thanks.
My control is 110K close enough to yours.
I install things daily and god knows what did it.
I also noticed the same thing happening with my Internet Transfer control.
Is there a website where I can download a fresh set of thesee ocx's (I know there are I just need a url).
And what do you mean by check the path of the winsock control?

-cl

First, I don't know of where you can download these OCXs. Maybe do a websearch.

Second, I mean that you *may* have multiple copies of some OCXs on your machine. If you do, be sure that the one you've loaded is the right one. If you look at Project - Components, it tells you the location of every control it's using. If you have multiple copies, you can change this location.

"I have a plan so cunning you could put a tail on it and call it a weasel!" - Edmund Blackadder

Gotcha.
That I did already.
Thanks anyway.
Anybody else who could offer advice?

-cl

Reinstall VB, then reapply SP4. Don't uninstall, just select reinstall all components. The license information is stored in the registry, not in the OCX itself. Reinstalling will add the appropriate key. I don't know exactly where it is, but if you found it on another workstation, you should be able to extract it and import on the other side.

Trust me, I've already been that route and it doesn't work.
I am using the learning edition of VB and am having problems with the winsock control.
I am wondering whether or not I should even have a license for winsock control OCX.
If anyone could send me a registry backup file of just the keys which contain the licensing information for winsock I would be greatly appreciated.
Thanks.
-cl

Ahh... You have learning edition. That is why you can't use it. Officially, it doesn't come with a license to use most of the controls. You really should upgrade, although, I would wait for VB.Net or subscribe to MSDN universal! Of course there is always the registry hack...