Hi, Thank you Everybody who vested their valuable time in replying me. Thanks Vernon Cole Thanks Michael.
Michael, As you said,i have downloaded the latest version of pyodbc and tested with it. same issue comes up again. Other facts i noticed while testing : 1) The script just exists with return code 128. 2) Sometime after(approx 20-30 mins) if i run the scripts,i was able to connect and no crash found. 3)After establishing the connection,if we terminate (Keyboard Interrupt)the script without closing the connection and once again try to connect,python.exe crashes The scripts terminates abnormally and doesnt give any traceback. i can see the dumps only when i reboot the machine. Please let me know if you need some more information. Thanks and Regards, Siddhartha On Wed, Dec 17, 2008 at 10:20 PM, Michael Kleehammer <mich...@kleehammer.com > wrote: > I am the correct developer, so we'll get started. > > The first thing we should do is try the latest pyodbc: > http://code.google.com/p/pyodbc > > There are a number of fixes in this new version, so it might be what > you need. (If so, let me know, though.) > > If the crash occurs in the new version, we'll also want to open a bug > report since it might help others. > > Next, we'd want to do 2 things: > > 1) Get an ODBC trace, which will tell us if one of the ODBC calls > failed and pyodbc crashed trying to cleanup the connection. > 2) Try the same test with a Unicode connection string: cnxn = > pyodbc.connect(u"..."). The first thing pyodbc does is convert the > string to Unicode and try the Unicode connect function, so perhaps > there is an error there. > > Thanks for the report and sorry for the trouble, > Michael Kleehammer >
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
