Re: [ODBC] Connectivity error: Could not convert from the current locale to wide characters - Mailing list pgsql-odbc

From Andrus
Subject Re: [ODBC] Connectivity error: Could not convert from the current locale to wide characters
Date
Msg-id B0AC90092A5B4A3895F18099C5AAAF05@dell2
Whole thread Raw
In response to Re: [ODBC] Connectivity error: Could not convert from the currentlocale to wide characters  ("Inoue, Hiroshi" <h-inoue@dream.email.ne.jp>)
Responses Re: [ODBC] Connectivity error: Could not convert from the currentlocale to wide characters
List pgsql-odbc
Hi,

Thank you.

>Could you turn on the Debug option in Advanced options (DataSource) page As 
>well?

I looked into all pages 1-3 ion advanced options.
There is no Debug option in any place in ODBC config.

Aslo in page 1 (screenshot attached) it looks like driver tries to write 
logs into root directory in c: drive.
In my knowldedge, this is disabled by default in newer windows OSes.
I can turn of Windows ODBC tracing and send this log if it helps.

Andrus.

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc

Attachment

pgsql-odbc by date:

Previous
From: Matej Mihelič
Date:
Subject: [ODBC] A POSSIBLE BUG: The ODBC standard procedure call ("{ CALLfunction(param) }") is disallowed in ReadOnly ODBC mode whereas "SELECT *FROM function(param)" is let through.
Next
From: Matej Mihelič
Date:
Subject: [ODBC] Q: Is there a way to force psqlODBC with enabled UseDeclareFetch tocommit statements and avoid nesting transactions (savepoints)?