Perry,

>In 2005 there is are new options under the Data Menu, View or Add a Data Source. <

I notice that if you choose "Object", you can then browse your projects in your solution and choose your Typed DataSets, which, to me, is the only kind of "data" you should have "attached" to your Form or control.

This whole business of having data access code directly on your Form because you want to do "drag-and-drop programming" is just wrong and I wish the wizards and such would not promote this kind of programming. (I see that you offer a similar opinion as well that this isn't ideal and I wholeheartedly agree.)

Just one of my pet peeves ... sorry to rant. <g>

~~Bonnie




>In 2005 there is are new options under the Data Menu, View or Add a Data Source. This option will let you select some options and generate code from them. This includes picking the type of control you want a particular piece to be attached to when you drag it onto your form.
>
>When you select to add a new Data Source, you are given the option of Database, Web Service or Object. This option isn't ideal since it generates data code as part of your form. But it does offer a lot of flexibility.
>
>PF
>
>
>>Perry,
>>
>>>And the only thing different between having access to a local data store and accessing a web service is the initial step of defining your data sources.
>>>
>>>So there is actually very little in the book that refers to web services because it's not too different from any other form of data access.<
>>
>>I'm not sure I understand what point you're trying to make. Could you elaborate a bit on this?
>>
>>~~Bonnie
>>
>>
>>
>>
>>>I am currently reading an excellent book, "Data Binding with Windows Forms 2.0" by Brian Noyes.
>>>
>>>His book doesn't have a particular focus on web services. Because he is focusing on strongly typed data sets. And the only thing different between having access to a local data store and accessing a web service is the initial step of defining your data sources.
>>>
>>>So there is actually very little in the book that refers to web services because it's not too different from any other form of data access.
>>>
>>>>>
>>>>>On your question, I use either web services or remoting, for the client piece to access the application layer (middle-tier). The application layer in turn accesses the data layer.
>>>>>
>>>>
>>>>One more question, and I will stop bugging you <g>. Can you recommend a book (for VERY beginner) on how to build what you call "application layer (middle-tier)" with Web Services?
>>>>
>>>>Thank you.