ODBC works, and there are bridges from ODBC to every other database technology (like DBX, for example). If the bridge doesn't work, then it's broken, and should be fixed. ODBC is also the closest to a standard that Microsoft supports, so it is probably the best one to use.
Well and ODBC-bridge for OLEDB exists, and even though it is written by Microsoft it caused many troubles. You may ask with which ODBC-driver i used it, well, it was the MS-Access ODBC driver.
Such a bridge always causes some overhead, and it may just not be possible with ODBC to achieve some of the functions that the bridge would need to be 100% compliant.
Of course it might be more convenient if there were ADO or .NET drivers for SAPDB, but it would be taking time that could be spent improving SAPDB in other ways.
Who want's a database without a client-API?
I also an concerned about the new licensing model, but we are prepared to maintain our own fork of SAPDB.
*eg* ;-)
But we should all maintain _one_ fork of SAPDB, since we'll need all our power to understand and improve SAPDB.
I should note that SAPDB also isn't directly supported by Gnome-DB (but since ODBC is...).
I'm very glad that ODBC for UNIX get's more popular, although i never could answer the question, if ODBC is a good API or not.
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
