I agree. My other approach (busy developer's approach :) is to tell the 3P vendor. You want the business of my customer, create Web Services for both Send and Receive (not sure if this is the right terminology). We will see what they say on this "suggestion"
Thank you.
>I would go restful WebAPI then. You don't know what's on the other end and it's possible that it could be used by another 3P customer.
>
>
>>First, thank you for your input (although most is way over my head, unfortunately). And I don't know if this is a .NET to .NET. The situation is as follows. A company approached my customer and they want to implement their application. But my customer insists that the records of this (3P) application have to be duplicated (or entered) into my application SQL Server. So I have to (it is up to me) suggest/direct how their data can go into my application database. This is why I thought of Web Services. But this other company, when creating a Web Service (my understanding is that they have to) may not use .NET but some other technology.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
