>>I'm working on a file with a developer who is creating the file.
>>One of everal choices he proferred for exchanging the file was "Web Service Transmission"
>>What is that and how would I receive the file?
>
>Web Service is great for communication among peers, thus, also not specifically without the organization but also with other companies. Information can be exchanged on a specific protocol.
>
>Web Service are usually not that difficult to build. There are a lot of samples on the Internet on how to do it in .NET.
>
>XML transmission would be an universal way of transmitting data over a Web Service. More sophistaced approaches would make use of objects.
>
>I, personally, prefer to remain with a XML approach as I find that easy to use and evolve.
>
>As for your needs, when I had to do something like that, I simply converted the file into a Base64 encoding, from the client side, and applied the reversed process on the server side. Once encoded, it can then be transmitted as is in XML, as one of the method parameters, for example.
>
>There are technology trends on the usage of Web Service, especially in .NET. My suggestion is, no matter what is used as far as technology, to simply keep it sample. Then, later on, if adjustments are to be done, or migration into another environment, it then becomes easier.

Thank, Michel
I'll look further.