OK I grabbed Connection, Qresult, Results, And convert off csv.
Does that get me up to date using the snapshot as the original source (also it converted to .net when I opened it and is compiling ok, so I must of mucky-mucked it up trying to create the project in .net).
Joel Fradkin
Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305
jfradkin@wazagua.com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
© 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc
This email message is for the use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and delete and destroy all copies of the original message, including attachments.
-----Original Message-----
From: Dave Page [mailto:dpage@vale-housing.co.uk]
Sent: Thursday, July 21, 2005 3:20 AM
To: Joel Fradkin; pgsql-odbc@postgresql.org
Subject: RE: [ODBC] what is best way to get the latest libpq version.
From: pgsql-odbc-owner@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Joel Fradkin
Sent: 20 July 2005 21:14
To: 'Joel Fradkin'; pgsql-odbc@postgresql.org
Subject: Re: [ODBC] what is best way to get the latest libpq version.
I compiled the snapshot version ok in visual studio 6 version of C++ (couldn’t seem to figure out the .net configuration, but I am not a c++ guy).
I did get one warning
d:\joel\wazagua_src\psqlodbc\results.c(3063) : warning C4101: 'conn' : unreferenced local variable
Is this something I need worry about?
Also is that the most fixed code or do I need to get on a csv or something.
That warning is fixed in CVS already, but no, you don't need to worry about it. CVS is always the most up to date code, and does have some major memory leaks fixed which are in 08.01.0001.
/D