Not really coding help but:
http://img221.imageshack.us/img221/5...mission4yx.jpg
ideas/suggestions/etc
For a friend, but I think it might be that he got an illegal/cracked version of VB.
Printable View
Not really coding help but:
http://img221.imageshack.us/img221/5...mission4yx.jpg
ideas/suggestions/etc
For a friend, but I think it might be that he got an illegal/cracked version of VB.
It isn't necessarily an illegal copy. What kind of control is causing the problem?
um...winsock controlQuote:
Originally Posted by MartinLiss
Are you using the windsock control? If not which controls are you using? There is a licensing issue wth certain control sometimes.
Yea its winsock...he said its giving him that message when he tries to "place a winsock control on the form"Quote:
Originally Posted by RobDog888
I cant find the post right now but there is a KB article over at MS about this issue. I'll keep looking.
You friend must have at least VB6 Pro.
I posted a link last night that had a copy of Winsock available for download. I just Googled it, and found it. Not sure if it worked out or not, though.
Just found it.
http://www.vbforums.com/showthread.php?t=376050
Seems that you may have the Learning edition which does not support windsock.
Yes, Dave but if he has anything less then Pro it will give the error since he probably downloaded in the first place to get it in his toolbox.
If you are NOT using VB Learning edition, check out this link:
http://support.microsoft.com/kb/194751/EN-US/
That tool fixed a problem I had with COMCTL32.OCX (another control, but the same error message).
There is a list with all controls this tool works with, and Winsock Control 6.0 is there.
I think this happends when you install a program that copies a new version of the OCX and register it, that version hasn't development licenses, its for runtime use only, so you open VB and it will try to use that OCX instead of the one it should use. this tool fix that, making VB work with the correct version of the OCX.