A dotNet driver is only going to help SAPDB / MaxDB.
No, it's going to cost money and time to develop and maintain and it's going to help microsofts loonie-platform gain credibility.
If people want to write cross platform programs they are better of using Java, if they want to write windows programs then it's only fitting that they bear the full pain of the bysantine windows api and language selection.
That still true, but it Mono might become a good choice for cross platform development too, although that might take some years.
Until Mono has gone somewhat stable and has a usuabl APi, i wouldn't write a SAPDB driber too, but hey, Stephen was talking about Windows development.
I would add that our testing has shown what Daniel says to be true. Using Perl on Linux or using dotNet on Windows we find SAPDB to be one of the most unreliable and poor performing database systems :)
I use SAP DB via DBD::ODBC from Perl on Linux and have for years and I havn't seen those stability problems once I made my aplication use ODBC correctly (close result sets and so forth).
Well, you're using ODBC, and i guess Stephen can't use ODBC any more since it is poorly supported by .NET ...
Why can't a C# driver link to the ODBC driver?
Surely he could, but you'd reinvent the wheel because you're just writing yet another ODBC bridge.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
