For the most part this is true. Datasets are inherently disconnected so it doesn't care where the data came from and how it was persisted. If you run locally against SQL server the data is still disconnected. When you run with a Web Service that passes the data back the Web Service is the local data, then sends that data back over the Web Service. The data nor the dataset content don't change in this process.

So as far as the ADO.NET is concerned it can't tell the difference.

+++ Rick ---

>Probably a silly question, but...
>
>Suppose I have two apps...
>
>App 1 is a WinForm app that talks 'directly' to SQL Server
>App 2 is also a Winform app, but uses a web service to access SQL Server.
>
>Would there be any real difference between a dataset created in app 1, versus app 2 (where a dataset is created by a web service and passed down to the Winform).
>
>Someone told me that there are differences in the way you'd use ADO.NET to work on the dataset locally under app 1 versus app 2...and I don't see how. I realize that any updating of data back in SQL would take on a very different form...but it seems that me that once you have a dataset, it doesn't matter 'how' you got it, you have access to the same ADO.NET properties for the dataset, regardless.
>
>True?
>
>Thanks,
>Kevin