Hi Tashler, No - I was not able to track down the cause. It is difficult to reproduce on demand for us, as it tends to be related to high concurrency situations (when the driver is waiting on the server, especially multiple trackings). We have spent hundreds of hours trying to isolate the factors that cause it...
As a short-term measure we took to seralizing all the calls the SAPDB ODBC driver and the problem went away... so it surely appears to be a issue within the driver of having multiple outstanding server connections. Long term we are likely switching to a commercial DB product that has better drivers. This problem has been 'death by 10,000 cuts' for our business. Stephen Gutknecht -----Original Message----- From: Taschler Raimund [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 19, 2003 6:53 AM To: '[EMAIL PROTECTED]' Subject: Win32 ODBC driver crash in sqlod32.dll Stephen, when searching the web I found that you've had the same problem in october 2002 I actually have: http://listserv.sap.com/pipermail/sapdb.general/2002-October/031626.html Could you track down the error? If so, please let me know your solution. Thank you in advance, Raimund _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
