Re: debug=1 supposed to be working? Any clue where I should

I will check that out (it is being called in a asp page which uses
II_USERmachineName.).

Thanks for the tip.

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: Thursday, July 21, 2005 10:34 AM
To: Joel Fradkin; pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] debug=1 supposed to be working? Any clue where I should
look to see why I always get a catastrophic error when I enable it?

_____

From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Joel Fradkin
Sent: 21 July 2005 15:18
To: pgsql-odbc(at)postgresql(dot)org
Subject: [ODBC] debug=1 supposed to be working? Any clue where I should look
to see why I always get a catastrophic error when I enable it?

On my freshly compiled libpq version, is debug=1 supposed to be working?

Any clue where I should look to see why I always get a catastrophic error
when I enable it?

Catastrophic failure is returned from my connection object with a connection
string of:

DRIVER={PostgreSQL};DATABASE=wazuni;SERVER=192.168.123.252;PORT=5432;UID=pos
tgres;PWD=1brain;ReadOnly=0;Protocol=6.4;FakeOidIndex=0;ShowOidColumn=0;RowV
ersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=100;Socket=4096;UnknownSi
zes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debug=1;CommLog=0;Optimizer
=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;UnknownsAsLongVarchar=0;Bool
sAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePrefixes=dd_;LFConversion=
1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus1=0;BI=0;ByteaAsLongVarB
inary=0;UseServerSidePrepare=0

Works ok without debug, but I am trying to isolate errors in my app.

Works for me. Does the user account under which your app is running have
permission to create and write files to C:\ ?

Regards, Dave.