From: Americo Motoya
Date: March 18 1999 9:32pm
Subject: En: Memory Leak
List-Archive: http://lists.mysql.com/myodbc/57
Message-Id: <000b01be7186$d3200540$3a12d3c8@millenium>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi Monty,

I have the trace files and I can see some error messages from MyODBC. But I
can't overpass them. What does this errors mean?

Sorry, I put the log files at  ftp://www.mysql.com/pub/mysql/incomming .

Thanks for the moment.

Best regards,

Americo

>
>Americo> 5 -Conclusion:  So I think the problem is  between ASP and MyODBC.
>Americo> I have tried MyODBC version 2.50.19 and  2.50.21 (for Win95) with
debug
>Americo> features and the optimized versions.
>Americo> Options: "Return matching rows" as described in MyODBC Readme
file.
>
>Americo> I asked my colleague to test that for me in another machine and
the result
>Americo> is the same. What are we doing wrong ?
>Americo> ADO is not a good partner to MySQL/MyODBC ?
>
>It's likely that ADO doesn't call functions that a ODBC program should
>call and it assumes that the ODBC driver will free some things
>automaticly.
>
>Can you generate a MyODBC trace file of the above test;  From this I can
>find out what what doesn't get freed!
>
>As this will probably be quite big, please ftp this to:
>ftp://www.mysql.com/pub/mysql/secret !
>