I couldn't think of better name. I'm open to suggestion.

I was considering create a class for each entity, User, Prospect, Client... Each class would basically have
the same methods and work the same, except tailored to the entity. Makes for a lot of coding up front, but seem like less confusion later on.


By the way - I've run it and I get the user rec back as XML. Very nice. My firt time ever
using a WS!!!!!





>Yes, it sounds good. Everything goes through the WS, whether the user is on the network or not. Perfect!!
>
>I don't know as though I like the names CSDataAccess and SSDataAccess, but that's just me. <g>
>
>~~Bonnie
>
>
>
>
>
>>Ok, I think I figured out what I want to do and I am trying to finalize a proof of concept.
>>
>>I have created a basic web service. As you described earlier, it will simply be a conduit for passing XML to and
>>from the Client and Server.
>>
>>I have set up a client side data access class (CSDataAccess) that converts datasets to XML and passes it to the WS.
>>I have also created a server side data access class (SSDataAccess) which performs queries against the DB into a
>>dataset, converts the dataset to XML and passes it back through the WS to the client.
>>
>>In the WS, I don't see a References node in the Solution Explorer. How do I add a reference to my SSDataAccess
>>class to the WS solution?
>>
>>
>>
>>[UPDATE] Found it.
>>
>>How does my concept sound?
>>
>>
>>
>>
>>>>Follow up question on this:
>>>>
>>>>The customers will have some users directly accessing the network and some remote, hence the need for a
>>>>web service. Should I create a data access class for direct connection as well as the WS, or just use the
>>>>WS for all data access?
>>>>
>>>>Inquiring minds wanna know.
>>>
>>>Depends on what you mean by directly accessing the network. <g>
>>>
>>>Typically, IMHO, a Web Service should be no more than a pass-through of parameters. A call to a web service method, simply passes the call along to a Business layer (which will, at some point, call methods in a DataAccess layer).
>>>
>>>With this architecture, anything that is already server-side (like a web app) would directly access the Business layer instead of accessing it through the web service (since they're both on the web server).
>>>
>>>Make sense?
>>>
>>>~~Bonnie