> 2. I already saw complains about lack of better documentation and I > wondering if there is more "organized" documentation, may be before was > released as open source?
We did not remove the "organized" documentation before releasing SAP DB as Open Source. But having two package formats (.rpm and .tgz), two vastly different platforms (Unix and Windows) and three different tools (DBM GUI, Web DBM, dbmcli) makes it just a bit harder to write that one document that answers every question in a jiffy. This does not mean that we won't keep trying. > 3. In teched2002.pdf is a reference to SQLCLI interface but there is no > reference to it at www.sapdb.org. I'm thinking on write a dbExpress (Delphi > / CBuilder) driver for SAP DB and I would like to use "native" API call > instead of ODBC. This is simply TLA (Three Letter Acronym) overload. The CLI stands for Command Line Interface, not for Call Level Interface. SQLCLI is the new name for a simple command line tool to execute SQL commands. It is currently called ireport, but we want to name it similar to dbmcli and loadercli. You should use ODBC, because this is the native API to SAP DB. If you create an import lib for sqlod32.dll, then there is no need to actually install the ODBC driver on the client machine, thus simplifying the distribution of your dbExpress driver. Note that you'll have to redistribute several other DLLs as well (sqltcp.dll, sqluser73.dll or sqluser74.dll). It would be possible to create one static library for Windows as it is done for Unix. Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
