Kevin,

First I believe the vendor's web service was developed in VS 2003 & possibly .Net framework 1.1 (not sure if this is relevant).

Their documentation states the web service will return an array which they convert to an arraylist (which is then bound to a grid, etc.) in their samples.

Should I consider converting the array to a dataset/entity instead (in business layer or other project of classes), for binding & data manipulation purposes?

Since I will be potentially developing web, windows form & PocketPC UI's for this web service would I be best served in creating a business layer with the web reference (if that is doable ie. WS, BO, UI vs. BO, WS, UI)?

If so the business layer generator seems to only reference tables, views & SP's...suggestions?

I believe this would all be easier if their license allowed me utilize the MM.Net framework to create a web service.

I hope I am not too wayward, Ted

>Ted,
>
>>I am just asking for some guidance/reference materials....
>>
>>1. Since the web service exists would I have any need for creating BO's or data access classes?
>>2. Would I just need to add a web reference to my web form project?
>>3. Any other helpful hints/gotchas I should research?
>>
>>I imagine the vendor has done some of the heavy lifting for me, but I still would like to implement an approach which will best utilize the MM.net framework & philosophy.
>
>The answers to these questions depend on what the web service returns and what you want to do with what it returns to you. For example, if it returns a DataSet/DataTable/Xml that you want to manipulate, you can create a business object that performs the manipulation for you. You can use the business object's SetCurrentDataSet() to assign a DataSet to a business object.