Thanks Bruce.
I was't suggesting that there was anything wrong with what Nettalk was generating as such, it just seems to be how my other development environment interprets the WSDL file. If anything, I might have suggested that a Real maps to a Float??
I experimented by manually changing the WSDL file without doing anything to the nettalk server, and xs:float, xs:string or xs:int seemed to cause problems, in my client application, but xs:long worked fine.
I just wondered if there was a way that I could put something into the code that would override these fields so that I don't have to remember to manually change them each time.
Regards,
Neil.