> -----Original Message----- > From: Erick Thompson [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, April 30, 2002 6:58 PM
> If you are using a DataSet or DataTable, couldn't you define > an interface for doing updates/inserts/deletes, and generate > the SQL at runtime, based on the contents of the > DataSet/DataTable. > I guess what I'm saying is to reproduce SqlCommandBuilder, > but for other databases. Because your command builder is > specific to your application, you could force it to use > stored procedures, or any other db specific function. SqlCommandBuilder sounds a lot like the Option #3 I was thinking about. The rub is that you'd need to write one for each DBtype and it provides no general interfaces to leverage. Looking at the class it looks very purpose built - to push back DataSet changes. > The select command becomes the only difficult part. For that, > I think your 3 options would all work, plus #4, use ANSI SQL 92 :) Believe me - I'd love to! :P Jim You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
