Re: ERROR - no error information available

Thanks for your help Luf, I sincerely appreciate it! I am not familiar with
the ODBC log format and the items in it, so I can't truly make heads or
tails of it. Your help was of great service! If the log is not showing
anything out of the ordinary, then it might be something else.

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
data into the database for testing purposes, however, this **shouldn't**
have caused any grief like this. I mentioned before, the SQL statements were
tested outside of the code using psql. Weird.

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.

I will keep digging at it. Let me know if new suggestions pop-up! :)

Regards,
dw

-----Original Message-----
From: Ludek Finstrle [mailto:luf(at)pzkagis(dot)cz]
Sent: Wednesday, December 07, 2005 3:52 PM
To: DWilkerson
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: [ODBC] ERROR - no error information available

> I apologize for not being clear the first time. Below is a snippet from my
> log that I think maybe the suspect. The SELECT statement below is one (of
> many) from the code that is dying. I have attached my whole mylog file
too.

I can't make you happy. I see no problem in whole mylog :-(
If I don't reproduce it here I can't help you. I'm sorry.
The first "error" is SQL_SUCCESS_WITH_INFO and there isn't supported
SQL_DTC_TRANSITION_COST in SQLGetInfo in the second one.
But both situation are ok.

Could you trace your program and said me where the error raise?

Regards,

Luf