🚀 go-pugleaf

Thanks ... i am not mixing any other components, just as a test i created a
New Service application and just placed the IdHTTP Client component on there
... the errors were as noted.

I did search deja.com and found a suggestion to use the define statement:-

#ifndef _WINSOCKAPI_ // magic incantation to avoid windows calling in
winsock.h
#define _WINSOCKAPI_
#endif

that seemed to work.

Thanks again
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:42681a0b$1@newsgroups.borland.com...
>
> "No-Spam" <No-Spam@NoSpam.com> wrote in message
> news:426815f6$1@newsgroups.borland.com...
>
> > I've update to indy 9.14, when adding a IdHTTP Client to
> > the service, the compiler reports Multiple declaration errors.
>
> Indy uses WinSock v2.0.  Most VCL socket components, including the ones
that
> ship with BCB, still use WinSock v1.x instead.  The headers for the two
are
> not compatible with each other.  winsock2.h disabled winsock.h if
winsock2.h
> gets included by the preprocessor first, but if winsock.h is included
first
> then all hell breaks loos.  Don't mix other socket components with Indy.
If
> you do a search in the newsgroup archives at http://www.deja.com , you
will
> see this issue discussed many times before.
>
>
> Gambit
>
>