Hi all; overally, after a longer session of issue-tracking and communication, there's a solution to the ODBC driver loading problem using maxdb - ODBC 7.05.00.00 on MS Windows NT 4 platforms.
> > [Mon Aug 30 02:54:22 2004] DbException: Specified driver could > > not be loaded due to system error 127 (SAP DB). [IM003] A closer look shows that the ODBC driver refuses to load because the function GlobalMemoryStatusEx in kernel32.dll is missing. This function apparently is not present in pre-Windows 2000 kernel32.dll and therefore the ODBC client (same as, obviously, the server, see http://lists.mysql.com/maxdb/20413 ) is not working on MS Windows NT 4.0. Workaround: * SAPDB ODBC 7.4.x obviously also requires GlobalMemoryStatusEx to be happy; ODBC 7.3 drivers seem to work well. * If you get SQLStudio installed and running with an sqlod32w.dll, Version 7.05.00.00, date 09/02/03, you might want to try the SQLSTUDIOODBC driver to connect to the database which works well here and obviously doesn't "suffer" from the GlobalMemoryStatusEx "issue". Many thanks to Thomas Koetter @ SAP for helping me getting through this. Cheers, Kris -- Kristian Rink -- Programmierung/Systembetreuung planConnect GmbH * Strehlener Str. 12 - 14 * 01069 Dresden 0176 24472771 * [EMAIL PROTECTED] -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
