> I have a VB6 project which used to contain a Winsock control. Somehow,
> the Winsock has become a PictureBox. I've seen that behaviour before -
> VB likes to replace any control it can't load with a Picture Box
> control with the same name. Well, there's no Winsock showing in the
> toolbox, so I'll try and put it back. So, off the menus, Project -
> Components - (Controls tab) ... scroll down ... there it is -
> 'Microsoft Winsock Control 6.0 (SP5)' - and it isn't checked. I'll
> check it. Click Apply. I get the message 'Name conflicts with existing
> module, project, or object library'. Well, there's nothing in my
> project named Winsock (although there was until I renamed a Property
> Set in one of my classes from 'Winsock' to 'Socket', but that didn't
> help.

> Any ideas?

> Andy Ellis

> The VB project file (vbp) has become corrupted.

> Take a copy of it and then open it in Notepad - Delete the line
refering to
> the Winsock control, save the vbp, and reopen in VB.

> You should now be able to add the Winsock back in via Components.

> --
> Rob

> Why not ask for a low cost development quote from our MCSD qualified
staff

> http://www.dotNetDevelopment.co.uk/

> > I have a VB6 project which used to contain a Winsock control.
Somehow,
> > the Winsock has become a PictureBox. I've seen that behaviour
before -
> > VB likes to replace any control it can't load with a Picture Box
> > control with the same name. Well, there's no Winsock showing in
the
> > toolbox, so I'll try and put it back. So, off the menus, Project -
> > Components - (Controls tab) ... scroll down ... there it is -
> > 'Microsoft Winsock Control 6.0 (SP5)' - and it isn't checked. I'll
> > check it. Click Apply. I get the message 'Name conflicts with
existing
> > module, project, or object library'. Well, there's nothing in my
> > project named Winsock (although there was until I renamed a
Property
> > Set in one of my classes from 'Winsock' to 'Socket', but that
didn't
> > help.

> > Any ideas?

> > Andy Ellis