Re: ODBC changes

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: ODBC changes
Date: 2001-09-12 10:34:08
Message-ID: 8568FC767B4AD311AC33006097BCD3D61A2E2D@woody.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

> -----Original Message-----
> From: Hiroshi Inoue [mailto:Inoue(at)tpf(dot)co(dot)jp]
> Sent: 12 September 2001 11:31
> To: Dave Page
> Cc: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] ODBC changes
>
>
> Dave Page wrote:
> >
> > Hiroshi,
> >
> > I've been playing with this new version a little and am seeing some
> > differences with the error messages raised. It's difficult to tell
> > exactly what's going on because my own code is somewhat 'in
> limbo' at
> > the moment, but with 07.01.0006, if I try to connect to a server
> > that's not running I
> > get:
> >
> > 2001-09-12 08:51:14 - Error in pgAdmin
> II:frmConnect.cmdConnect_Click:
> > -2147467259 - Could not connect to the server; Could not connect to
> > remote socket.
> >
> > But with 07.01.0007 I get:
> >
> > 2001-09-12 08:54:46 - Error in pgAdmin
> II:frmConnect.cmdConnect_Click:
> > -2147467259 - Unspecified error
> >
> > The errors reported by pgAdmin II are as returned by ADO
> from the ODBC
> > driver. Any ideas?
>
> Hmm it seems to work if I remove ODBC3.0 functions from
> psqlodbc_win32.def.

Ahh, could it be that ADO is using SQLGetDiagRec instead of SQLError because
it thinks it's ODBC3.0? If so, that would tie in with some of the other
oddities I've seen with my code (which is calling SQLGetDiagRec directly).

Regards, Dave.

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Henshall, Stuart - WCP 2001-09-12 13:59:05 Re: 'ODBC call failed' a few seconds after Opening the tab
Previous Message Hiroshi Inoue 2001-09-12 10:31:12 Re: ODBC changes