>I have been playing around with the WebService walkthrough in the MSDN documentation... and it really is a mouth full! I mean my head is already aching with design questions that still haven't been answered.<

Web Services are really not all that hard to implement. As far as design, the way we do it is to simply use a Web Service as a sort of wrapper around the Biz Objects. The Web Service methods do practically nothing except to gather the necessary parameters, call a Biz Object method and return data. We pass all DataSets, both to and from the Web Service methods, serialized to XML.

>>Based on what I have studied today, I was thinking that the application would perform much better if i used web forms instead of windows form. But from what I understand based on what you said... it really does not matter? I am actually just reading between the lines here and I hope I'm reading them correctly.<

Nope. Not what I said. IMHO, windows forms are preferable for a better user experience. A rich-client app can be more full-featured, UI-wise, than a thin-client app. There are definitely pros and cons to both, and it *does* depend on what you're trying to accomplish, so I can't just make a blanket statement one way or the other ... except to say that I prefer rich-client to thin-client for the types of apps I write.

Now, that said, one of the benefits to using a Web Service the way we have (a wrapper for Biz Objects) is that you can use those same Biz Objects for either UI and so you can utilize both WinForms and WebForms in your app. When used from the rich-client (WinForm), you access the Biz Objects via your Web Service. When used from the thin-client (WebForm), you can access the Biz Objects directly, since it's all server-side.

More food for thought! <g>

~~Bonnie