microsoft.public.dotnet.framework.odbcnet

Daniel Morgan

1/24/2003 10:18:00 AM

Why worry about ODBC when trying to create a .NET data provider? The
ODBC.NET data provider is for legacy reasons. If you're creating a new
provider, you might as well make it a fully managed .NET data provider.

Read this MSDN article about how to create a data provider.
http://msdn.microsoft.com/msdnmag/issues/01/12/DataProv/toc.asp?...

There are plenty examples on the .net to see data providers created.
For instance, the data providers found in Mono (.NET for Unix)
at http://www.go-mono.com/ad...

If you get the source code to mcs, and go to the class folder, you will find
providers
for IBM DB2, PostgreSQL, MySQL, Oracle, ODBC, Microsoft SQL Server, Sybase.

Also, there are other open source .NET data providers:

MySQL ADO.NET provider
http://sourceforge.net/projects...

PostgreSQL ADO.NET provider
http://gborg.postgresql.org/project/npgsql/projd...

Firebird SQL (based on Interbase) ADO.NET provider
http://sourceforge.net/projects...

"Mark K" <xxxxxx> wrote in message news:ucaI9rXwCHA.968@TK2MSFTNGP12...
> I'd like to write an ODBC driver to access a DBMS from a .Net client
program
> (vb, vc++, etc). Can anyone point me in the right direction?
>
> Thanks,
> Mark
>
>
>