From: | Ludek Finstrle <luf(at)pzkagis(dot)cz> |
---|---|
To: | DWilkerson <dwilkerson(at)ideorlando(dot)org> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: ERROR - no error information available |
Date: | 2005-12-07 21:51:36 |
Message-ID: | 20051207215136.GA1001@soptik.pzkagis.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> The funny part is that the driver I was originally using has been working
> fine for a long time. This just recently started happening. I loaded new
Do you change ODBC driver for PgSQL? What version had you used?
Could you create mylog with ODBC driver which was working properly?
> data into the database for testing purposes, however, this **shouldn't**
Are you sure? What about unicode chars? I see no unicode char but
traversing so much fetched rows ...
Did you try ANSI driver?
> The error(s) happen intermittently in the code when tracing. Sometimes
> things go nuts when it's in the initialization phase, and other times it's
> deeper in the app when buttons are clicked, etc. Again, weird.
Could you log in your application if ODBC driver return what you expect?
Regards
Luf
From | Date | Subject | |
---|---|---|---|
Next Message | Kathy Lo | 2005-12-08 02:59:03 | Where to get the latest source for Linux |
Previous Message | DWilkerson | 2005-12-07 21:42:23 | Re: ERROR - no error information available |