>>I think you misunderstood Morgan's comments. His main point is that it's not a good idea for a User Group's webpage to be hitting your WebService from their web page itself ... primarily because if your web server is down or slow, it will affect their webpage (it could time out or just flat out not work). He's simply saying that you shouldn't recommend that it be done this way and that you should recommend that they cache the info locally and have their webpage hit the local cache. How often it's cached from your WebService and how it's cached either via a service or a scheduled windows event, would be up to the User Group, but you might give some examples along that line too.
>
>Yes, I understood all that in his message and this is what I've been teaching as well. But, as I said, it was a requirement to deliver it as is. From there, if they wish to have a robot to process at interval then, they simply have to grab that VB.NET code and put it inside a VB.NET application instead.

No, you don't understand ... I'm saying that you're *recommending* putting the code to access your WebService in a web page by publishing that method of doing it. It doesn't matter that someone wants to do it that way, it's not the best way to do it and you shouldn't recommend to do it that way. In your directions for how to use the WebService, just change your example to show how to do it the correct way, rather than from a WebPage. That's all ...

~~Bonnie