Skip site navigation (1) Skip section navigation (2)

RE: ODBC Problem

From: László Tibor <ltibor(at)mail(dot)tiszanet(dot)hu>
To: <Jamz(at)AirNet(dot)Com(dot)AU>, <pgsql-interfaces(at)postgresql(dot)org>
Subject: RE: ODBC Problem
Date: 2001-07-18 10:32:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
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

  -----Original Message-----
  From: pgsql-interfaces-owner(at)postgresql(dot)org
[mailto:pgsql-interfaces-owner(at)postgresql(dot)org]On Behalf Of
  Sent: Wednesday, July 18, 2001 2:11 AM
  To: pgsql-interfaces(at)postgresql(dot)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, query='SELECT * FROM userservices WHERE printform=true AND

  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(at)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

  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,



  "We should have laser guns!"

        - Andrew Hill (Post Support Call)

In response to

pgsql-interfaces by date

Next:From: markMLl.pgsql-interfacesDate: 2001-07-18 13:05:08
Subject: Re: postgres access from windowsNT
Previous:From: Henshall, Stuart - WCPDate: 2001-07-18 09:09:07
Subject: RE: MS Access 97 SR-1, psqlodbc, slow perfomance

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group