Well for one thing, in your scenario you are creating twice the number of processes and a heck of a lot more necessary code.
Your scenario Get SQL Server data Write data to Access DB Get Access data Load into Dataset Manipulate data Save data to Access DB Update data from Access DB to SQL Server The common method Get data from SQL Server Fill Dataset Manipulate data Save data to SQL Server The advantage of loading tables into a Dataset (memory) is that you improve the performance of the application by reducing the number of hits to the database. If your database sets on a server then you are also reducing load on that server. Greg Ward ************************************ www.VB-FAQ.com VB Developer's FAQ site ************************************ > -----Original Message----- > From: The DOTNET list will be retired 7/1/02 > [mailto:[EMAIL PROTECTED]]On Behalf Of Avi Nahir > Sent: Sunday, June 02, 2002 9:21 AM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] DataSets naive question > > > Thanks, Greg. > > I undestand this "in memory" issue. However, what I'm thinking is: You are > supposed to take the data from a 'big' (say, SQL Server) database, work on > it in memory using a Dataset, and then return the modifications. But what > if, instead, you take the data, store it in an Access (Jet) database, work > on it (using possibly ADO.Net Command objects or dataset) and then, at your > leisure, return the modifications to the big database? > > The basic thing that bugs me: Being "in memory" is not enough merit for a > technology! I must be missing something. What? What is the advantage of > using an in memory Dataset as opposed to the scenario above? You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
