"Typed Datasets have a few minor issues ( eg remoting issues)" Sorry but I had to change the subject. I forgot to do so last time :(
If I.... 1) create a strong type dataset (dsServer) on the server and pass it to the client, which has a dataset defined (dsClient) on the form bound to a grid using the schema of my dataset (dsServer). 2) I assign dsClient to dsServer (same type of dataset) and let the user update the data in the grid. 3) Then they click the save button. 4) I create a dataset of the dsClient type and assign it the GetChanges of dsClient. 5) I then pass this smaller dataset to the server manager object which excepts a dataset of type dsServer (same as dsClient). The above senario works with remoting right? -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED]]On Behalf Of Ben Kloosterman Sent: Tuesday, October 08, 2002 7:46 PM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Strongly-Typed DataSets vs. Strongly-Typed Collections I got that from some conversation by the developers on the micrososft site. The main issue I have run into is typed dataTables are not serializable. Most people (including my self) use GetChanges and send the Dataset but this sends an untyped dataset. Regards , Ben You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
