This post originated from an RSS feed registered with .NET Buzz by Paschal. Original Post: Unified Data Access for .NET Feed Title: help.net Feed URL: http://www.asp.net/err404.htm?aspxerrorpath=/pleloup/Rss.aspx Feed Description: .Net for mankind ! Latest .NET Buzz Posts Latest .NET Buzz Posts by Paschal Latest Posts From help.net

I certainly going to use this article in a next dScribe release.

Philip Miseldine explain here how you can create a generic class to talk to any database. So you don't have to worry
about the connection (ODBC class type or SQL), but instead you have a generic interface to call your database.

Introduction

Nearly all of today’s Web applications use some sort of database to store persistent data. .NET applications often use SQL Server, PHP applications mostly use MySQL, and so on. When deploying an application to clients, however, there are many occasions on which they may wish to use a different database than that which your application has implemented. They might use Oracle throughout their enterprise, for example, and simply will not use your system as it stands without support for it. It is also far better practice to give the end-user choice rather than tying your system to a single third party database.

UPDATE: Frans Bouma make the point that it's good only for common SQL statements. If you use specific Oracle commands for example.