Re: figuring out why I am having this issue

The patch fixed the other issue (my sql was 8k so fixing connect did the
trick).
I manually applied the changes is there an easier way?

Again I appreciate all the help, I will test more to see if any other issues
come up, but at least my initial problem with the FE driver seems to not be
a problem in libpq land.

Joel Fradkin

Wazagua, Inc.
2520 Trailmate Dr
Sarasota, Florida 34243
Tel. 941-753-7111 ext 305

jfradkin(at)wazagua(dot)com
www.wazagua.com
Powered by Wazagua
Providing you with the latest Web-based technology & advanced tools.
C 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(at)vale-housing(dot)co(dot)uk]
Sent: Friday, September 02, 2005 10:19 AM
To: Joel Fradkin
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] figuring out why I am having this issue

> -----Original Message-----
> From: Joel Fradkin [mailto:jfradkin(at)wazagua(dot)com]
> Sent: 02 September 2005 15:08
> To: 'Joel Fradkin'; Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: RE: [ODBC] figuring out why I am having this issue
>
> Thanks to a bit of guidance from Dave and Merlin I now have
> the latest CVS
> source (using a CVS tool).
> I was able to compile via command line.
> I tried the latest build and the text issue did not come up
> (I could view
> and edit the text field giving me the issue).
> I however had host.dll give me a memory error trying to print
> preview, so I
> am looking at what might be the issue.

Ahh, well, host.dll definitely isn't ours!!

> I appreciate everyone helping me out as I know you guys are busy.
> I still cant believe I was using the old driver all that time
> (I am still
> using it in production, but hope I can resolve this memory blow out).

Hehehe. Of course, some of my unicode fixes applied to either version of
the driver which is why you probably didn't notice! Glad to hear the
problem's gone though.

Regards, Dave.