Received: from gauss.deltav.hu (mail.deltav.hu [213.163.0.9]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6IAWUa15167 for ; Wed, 18 Jul 2001 06:32:30 -0400 (EDT) (envelope-from ltibor@mail.tiszanet.hu) Received: from pcltibor ([213.163.10.100]) by gauss.deltav.hu (Netscape Messaging Server 3.6) with SMTP id AAA165C; Wed, 18 Jul 2001 12:37:28 +0200 From: =?iso-8859-2?B?TOFzemzzIFRpYm9y?= To: , Subject: RE: ODBC Problem Date: Wed, 18 Jul 2001 12:32:26 +0200 Message-ID: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0002_01C10F85.B403CEE0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200 Importance: Normal In-Reply-To: <9CA159BC716ED4119907009027F658330303AD@exchange01.office.adl.airnet.com.au> X-Archive-Number: 200107/74 X-Sequence-Number: 1828 This is a multi-part message in MIME format. ------=_NextPart_000_0002_01C10F85.B403CEE0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit I had a same problem with Win98SE. Some of our datasets showed wrong empty recordsets using C++Builder executable with ODBCExpress components and the latest driver. But after installed a newer MDAC (2.5 I think) it dissapeared. I didn't tried the latest MDAC. So nothing useful for you :-( Tibor Laszlo ltibor@mail.tiszanet.hu -----Original Message----- From: pgsql-interfaces-owner@postgresql.org [mailto:pgsql-interfaces-owner@postgresql.org]On Behalf Of Jamz@AirNet.Com.AU Sent: Wednesday, July 18, 2001 2:11 AM To: pgsql-interfaces@postgresql.org Subject: [INTERFACES] ODBC Problem Greetings people, Before I go nuts, I wonder if anyone has solved this problem before; I have been using the ODBC driver for our Postgres server to develop software in Visual Basic with great success until just recently. Symptoms of the problem are that queries on some machines execute correctly, but taking the same code and executing it on another machine returns empty recordsets. I made sure all the drivers were the same and that the latest MDAC 2.7 was installed on all machines. On further investigation, I found that on the affected machines, queries to tables with an index come back with an empty recordset. Win2k Terminal Server SP2: okay - queries return data WinXP Beta2: okay - queries return data WinNT4 Server: only queries on some tables return data Win2k Server SP2: only queries on some tables return data I guess this must be something to do with the setup of the ODBC driver on these machines, but I can't for the life of me find any difference in settings. All the machines use identical connect strings. I looked at the ODBC logs to find something that was failing and couldn't really see any thing bad: conn=35795448, SQLDriverConnect(out)='DRIVER={PostGreSQL};DATABASE=bmf;SERVER=bm f.some.domain;PORT=5432;UID=postgres;PWD=xxxxx;READONLY=0;PROTOCOL=6.4;FA KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS =' conn=35795448, query='SELECT * FROM userservices WHERE printform=true AND formpr inted IS NULL' [ fetched 1 rows ] conn=35795448, SQLDisconnect So it looked like the row I wanted was retrieved but the recordset still remained empty L I believe the server is running Postgres 7.0.3 : [root@bmf bin]# ./psql -V psql (PostgreSQL) 7.0.3 contains readline, history support Portions Copyright (c) 1996-2000, PostgreSQL, Inc Portions Copyright (c) 1996 Regents of the University of California Read the file COPYRIGHT or use the command \copyright to see the usage and distribution terms. All machines are using the same ODBC driver version 6.5, PSQLODBC.DLL 4/2/2000 If anyone knows if there is a known problem with this combo please let me know and I will have a case to get the admin to upgrade. Cheers & TIA, Jamz. =-=-=-=-=-=-=-=-=-=-=-=- "We should have laser guns!" - Andrew Hill (Post Support Call) ------=_NextPart_000_0002_01C10F85.B403CEE0 Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable
I had=20 a same problem with Win98SE. Some of our datasets showed wrong empty record= sets=20 using C++Builder executable with ODBCExpress components and the latest driv= er.=20 But after installed a newer MDAC (2.5 I think) it dissapeared. I didn'= t=20 tried the latest MDAC.
 
So=20 nothing useful for you :-(

Tibor Laszlo
ltibor@mail.tiszanet.hu

-----Original Message-----
From:=20 pgsql-interfaces-owner@postgresql.org=20 [mailto:pgsql-interfaces-owner@postgresql.org]On Behalf Of=20 Jamz@AirNet.Com.AU
Sent: Wednesday, July 18, 2001 2:11=20 AM
To: pgsql-interfaces@postgresql.org
Subject:=20 [INTERFACES] ODBC Problem

Greetings=20 people,

       &nbs= p;   =20 Before I go nuts, I wonder if anyone has solved this problem befor= e; I=20 have been using the ODBC driver for our Postgres=20 server to develop software in Visual Basic with great success until just= =20 recently.

 

Symptoms of the problem are= that=20 queries on some machines execute correctly, but taking the same code and= =20 executing it on another machine returns empty recordsets. = I=20 made sure all the drivers were the same and that the latest MDAC 2.7 was= =20 installed on all machines.

 

On further investigation, I= found=20 that on the affected machines, queries to tables with an index come back = with=20 an empty recordset.<= /P>

 

Win2k Terminal Server SP2: = okay -=20 queries return data

WinXP<= FONT=20 face=3DArial size=3D2> Beta2:=20 okay - queries return data

WinNT4 Server: only queries= on=20 some tables return data

Win2k Server SP2: only quer= ies on=20 some tables return data

 

I guess this must be someth= ing to=20 do with the setup of the ODBC driver on these machines, but I can't for t= he=20 life of me find any difference in settings.  All the machines use identical = connect=20 strings.

 

I looked at the ODBC logs t= o find=20 something that was failing and couldn't really see any thing=20 bad:

 

conn<= /SPAN>=3D35795448, SQLDriverConnect(out)=3D'DRIVER=3D{PostGreSQL};DATABASE=3Dbmf;SERVER=3Dbm

f.some.domain;PORT=3D5432;UID=3Dpostgres;PWD=3Dxxxxx;READONLY=3D0= ;PROTOCOL=3D6.4;FA

KEOIDINDEX=3D0;SHOWOIDCOLUMN=3D0;ROWVERSIONING=3D0;SHOWSYSTEMTABLE= S=3D0;CONNSETTINGS=3D'

conn<= /SPAN>=3D35795448, query=3D'= SELECT *=20 FROM userservices WHERE printform=3Dtrue AND formpr

inted= IS=20 NULL'

    [=20 fetched 1 rows ]

conn<= /SPAN>=3D35795448, SQLDisconnect

 

So it looked like the row I= wanted=20 was retrieved but the recordset still remaine= d empty=20 L

 

I believe the server is run= ning=20 Postgres 7.0.3=20 :

 

[roo= t@bmf=20 bin]# ./psql=20 -V

psql<= /SPAN> (PostgreSQL) 7.0.3

contains readline, history support<= /P>

Port= ions=20 Copyright (c) 1996-2000, PostgreSQL,=20 Inc

Port= ions=20 Copyright (c) 1996 Regents of the=20 University of=20 California<= /FONT>

Read= the file=20 COPYRIGHT or use the command \copyright to see=20 the

usage= and distribution= =20 terms.

 

All machines are using the = same=20 ODBC driver version 6.5, PSQLODBC.DLL 4/2/2000

 

If anyone knows if there is= a=20 known problem with this combo please let me know and I will have a case t= o get=20 the admin to upgrade.

 

Cheers &=20 TIA,

       &nbs= p;   =20 Jamz.

 

 

 

= =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-

= "We=20 should have laser guns!"

=       -=20 Andrew Hill (Post Support Call)

 

------=_NextPart_000_0002_01C10F85.B403CEE0--