Yes, there is a unique driver for the dotNet VM (CLR). ODBC can be supported, but performance suffers, and trying to debug it is difficult (good luck trying to debug a nasty C ODBC driver).
They are basically just called ".Net Data Provider". Here is background: http://msdn.microsoft.com/library/default.asp?url=/msdnmag/issues/01/12/Data Prov/toc.asp the MySQL .NET driver project: http://sourceforge.net/projects/mysqlnet/ PostgreSQL .NET driver Npgsql: http://gborg.postgresql.org/project/npgsql/projdisplay.php Firebird has firebird-net-provider: http://sourceforge.net/projects/firebird/ I believe there are others for mySQL (alternate projects). Part of the problem, at least for me, is that SAPDB's driver to server protocol is "rather unique". Someone who has skills to reverse / study the Python driver or Java (JDBC) SAPDB drivers would likely have an easier time than trying to just work from the protocol specification. Stephen Gutknecht -----Original Message----- From: Sven K�hler [mailto:[EMAIL PROTECTED] Sent: Friday, August 08, 2003 3:44 PM To: [EMAIL PROTECTED] Subject: Re: SAPDB not comptetive due to neglect of Win32 drivers Well, what kind of drivers does .NET use? Is there a .NET API like JDBC that's independant of ODBC, OLEDB etc.? _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
