hi, i had same problem. But after I put mysql_free_result(MYSQL_RES *pResult) after fetching rows from query (or generaly after calling all queries), it was OK without this message. I think there is a problem when you allocate memory for result of a query (with mysql_store_result(MYSQL *myData)), and you dont call mysql_free_result() to free this allocated memory, than memory leaks are detected, and Access Violation Error proceed.
----- Original Message ----- From: "Leo" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 29, 2003 7:24 AM Subject: Problem with mysql_close() API Hi All, i have a problem everytime i call the function mysql_close(), it result in Access Violation Error in module libmysql.dll fyi, im migrating from 3.23.52 to 4.0.x server runs under linux, im accesing the server through windows based application built with delphi, using Object Pascal translation from C API (by Jorge del Conde) with the library i took from mysql directory the flow is similiar like this: mysql_init(@myconnection); mysql_real_connect(@myconnection,...); ... some proccess ... mysql_close(@myconnection); <-- this is where the error raised i slip in mysql_init before mysql_close, and the problem disappear.. mysql_init(@myconnection); mysql_real_connect(@myconnection,...); ... some proccess ... mysql_init(@myconnection); mysql_close(@myconnection); <-- this is where the error raised is this normal?? is this how it should be? i've red the manual, and there is none mentioning that i have to do init before cloaing one. thanks for any comment -- Regards Leonardus Setiabudi IT Project Coordinator PT Bina San Prima, www.binasanprima.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
