Hi all I have an integration project that I recently built that uses SQL
Server exclusively as it's database. I have been asked to change it so that
it will also work with MySql and Oracle. I am thinking that a non-typed
DataSet and OleDb is the way to go.

Am I headed down the right path? Will this indeed work for me for multiple
vendors?

--
Thank you,
John

No. Use OracleClient for Oracle, SqlClient for SQLS, and whatever
provider works with MySql. There is no good end-to-end story for true
provider-independent code in ADO.NET. You will get halfway there, and
then hit the wall with data types, parameters and delimiters. It's
better to just plan your data logic around needing to branch for each
data source than to try to roll it up into one. At some point in the
future the Entity Framework will be the way to go for scenarios like
yours, but it's not quite there yet.

--Mary

On Wed, 6 Aug 2008 13:36:02 -0700, John A
<i-code4food (AT) newsgroups (DOT) nospam> wrote: