From len-morgan@xroadstx.com Thu Jul 9 17:51:24 1998 Received: from mail2.xroadstx.com (xroadstx.com [208.220.74.12]) by hub.org (8.8.8/8.7.5) with ESMTP id NAA21917 for ; Thu, 9 Jul 1998 13:51:24 -0400 (EDT) Received: from H233 (mnet01-20.xroadstx.com [208.234.65.39]) by mail2.xroadstx.com (8.8.8/8.8.8) with SMTP id MAA23155 for ; Thu, 9 Jul 1998 12:51:21 -0500 (CDT) Message-ID: <005901bdab62$05df31e0$0908a8c0@H233> From: "Len Morgan" To: Subject: ODBC Problem Date: Thu, 9 Jul 1998 12:50:11 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0056_01BDAB38.1C25CEC0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 This is a multi-part message in MIME format. ------=_NextPart_000_0056_01BDAB38.1C25CEC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I have successfully connected to PostgreSQL from Access97 and have even = been able to make a query that gets it's results from several tables all = at once. The problem is that no matter what I do, the ORDER BY clause = of the query is ignored. I have set the sort criteria and I have tried = with a pass-through query but the sorting always seems to come out in = the order of the subtables that are joined to my main table. I also have had a problem where I want to write a pass-through query but = can't get it to execute without bringing up the "Select Data Source" = dialog box. We are only ever going to use one data source and I know = what it is so why do I get this message EVERY time I run the query? Is = there some way to specify the DSN in the pass-through query so that I = don't have to have my users do this everytime? Thanks for your help, len morgan ------=_NextPart_000_0056_01BDAB38.1C25CEC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I have successfully connected to = PostgreSQL from=20 Access97 and have even been able to make a query that gets it's results = from=20 several tables all at once.  The problem is that no matter what I = do, the=20 ORDER BY clause of the query is ignored.  I have set the sort = criteria and=20 I have tried with a pass-through query but the sorting always seems to = come out=20 in the order of the subtables that are joined to my main = table.
 
I also have had a problem where I = want to write=20 a pass-through query but can't get it to execute without bringing up the = "Select Data Source" dialog box.  We are only ever going = to use=20 one data source and I know what it is so why do I get this message EVERY = time I=20 run the query?  Is there some way to specify the DSN in the = pass-through=20 query so that I don't have to have my users do this = everytime?
 
Thanks for your help,
 
len = morgan
------=_NextPart_000_0056_01BDAB38.1C25CEC0-- From byronn@insightdist.com Fri Jul 10 16:41:12 1998 Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id MAA29372 for ; Fri, 10 Jul 1998 12:41:12 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id MAA14364 for pgsql-interfaces@postgreSQL.org; Fri, 10 Jul 1998 12:14:02 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA38686; Fri, 10 Jul 1998 12:04:49 -0400 Received: from byronn by ceodev (AIX 4.1/UCB 5.64/4.03) id AA65818; Fri, 10 Jul 1998 12:04:49 -0400 Message-Id: <35A63B41.CC2274D7@insightdist.com> Date: Fri, 10 Jul 1998 12:03:13 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: Len Morgan Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] ODBC Problem References: <005901bdab62$05df31e0$0908a8c0@H233> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Len Morgan wrote: > > I have successfully connected to PostgreSQL from Access97 and have > even been able to make a query that gets it's results from several > tables all at once. The problem is that no matter what I do, the > ORDER BY clause of the query is ignored. I have set the sort criteria > and I have tried with a pass-through query but the sorting always > seems to come out in the order of the subtables that are joined to my > main table. > I have had this problem also, but for the life of me, I can't reproduce it now. I remember though, when I had the problem, if I turned on "Totals" and just had "Group By" for all the fields, it allowed me to order by whatever I wanted. It *seems* like a bug in Access? Try that and see if it at least has an effect. Also, what version of the odbc driver are you using? And, can you illustrate your query (what tables, joins, etc) so I could try to reproduce it? > I also have had a problem where I want to write a pass-through query > but can't get it to execute without bringing up the "Select Data > Source" dialog box. We are only ever going to use one data source and > I know what it is so why do I get this message EVERY time I run the > query? Is there some way to specify the DSN in the pass-through query > so that I don't have to have my users do this everytime? > Yes, I have this as well. I do not know any way to make Access save the Data source with the query. As far as I can tell, it is not the driver but Access forcing this behavior? Have you or anyone seen differently with other databases like Oracle? Byron From byronn@insightdist.com Tue Jul 21 22:32:25 1998 Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id SAA19407 for ; Tue, 21 Jul 1998 18:32:25 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.9.0/8.9.0) with UUCP id SAA04786 for pgsql-interfaces@postgreSQL.org; Tue, 21 Jul 1998 18:29:35 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA38381; Tue, 21 Jul 1998 18:18:51 -0400 Received: from byronn by ceodev (AIX 4.1/UCB 5.64/4.03) id AA72700; Tue, 21 Jul 1998 18:18:50 -0400 Message-Id: <35B513E5.729800C5@insightdist.com> Date: Tue, 21 Jul 1998 18:19:17 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: Len Morgan Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] ODBC Problem References: <005901bdab62$05df31e0$0908a8c0@H233> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Len Morgan wrote: > > I have successfully connected to PostgreSQL from Access97 and have > even been able to make a query that gets it's results from several > tables all at once. The problem is that no matter what I do, the > ORDER BY clause of the query is ignored. I have set the sort criteria > and I have tried with a pass-through query but the sorting always > seems to come out in the order of the subtables that are joined to my > main table. > We have learned a few things about the Microsoft Jet Engine since this mail. Access uses "dynasets" to handle data in query recordsets. If you don't need to update values in your queries, you can use a "snapshot" recordset, which can be faster. It also may help your order-by random problem. To do this in Access, try bringing up the "design view" of your query. Then right click and you should get a "Query Properties" box. There is a field called "RecordSet Type" which probably says Dynaset. If you set this to "Snapshot", your problem may go away. > I also have had a problem where I want to write a pass-through query > but can't get it to execute without bringing up the "Select Data > Source" dialog box. We are only ever going to use one data source and > I know what it is so why do I get this message EVERY time I run the > query? Is there some way to specify the DSN in the pass-through query > so that I don't have to have my users do this everytime? > This one we definately have figured out. When looking at your pass-thru query, go to "View" then "Properties" in Access. This will bring up a box of properties. There is one called "ODBC Connect Str" and it should be defaulted to "ODBC;". Simply add "DSN=" after the ODBC part and it won't keep asking you. Hope this is helpful. Byron From kin.chan@technologist.com Thu Jul 15 05:18:22 1999 Received: from hk.linkage.net (pop3.hk.linkage.net [202.76.4.9]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA71907 for ; Thu, 15 Jul 1999 01:18:22 -0400 (EDT) (envelope-from kin.chan@technologist.com) Received: from terence ([210.184.79.157]) by mail.hk.linkage.net (8.8.8/8.8.8) with SMTP id NAA00697 for ; Thu, 15 Jul 1999 13:18:19 +0800 (HKT) From: "Terence Chan" To: Subject: ODBC problem Date: Thu, 15 Jul 1999 13:21:29 +0800 Message-ID: <000301bece81$e55664e0$9d4fb8d2@terence.cetec.com.hk> MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal I have exported a table from MS Access 97 to PG via ODBC. I can see the file is exported to the correct place but psql complaining the table is not there. Please help. Terence From hannu@trust.ee Thu Jul 15 06:04:58 1999 Received: from kodu.home.ee (isdn-54.uninet.ee [194.204.0.118]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA78132 for ; Thu, 15 Jul 1999 02:04:58 -0400 (EDT) (envelope-from hannu@trust.ee) Received: from trust.ee (hannu@localhost [127.0.0.1]) by kodu.home.ee (8.8.7/8.8.7) with ESMTP id JAA00494; Thu, 15 Jul 1999 09:14:18 +0300 Sender: hannu@kodu.home.ee Message-ID: <378D7C3A.4682B800@trust.ee> Date: Thu, 15 Jul 1999 09:14:18 +0300 From: Hannu Krosing Organization: Trust-O-Matic =?iso-8859-1?Q?O=DC?= X-Mailer: Mozilla 4.5 [en] (X11; U; Linux 2.2.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Terence Chan CC: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] ODBC problem References: <000301bece81$e55664e0$9d4fb8d2@terence.cetec.com.hk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Terence Chan wrote: > > I have exported a table from MS Access 97 to PG via ODBC. I can see the file > is exported to the correct place but psql complaining the table is not > there. Are you sure that the file (and directories leading to it) are readable by the user postgres, or whatever your backend runs as ? As a last resort move the file to /tmp and chmod 777 it. ------ Hannu From kin.chan@technologist.com Thu Jul 15 06:19:40 1999 Received: from hk.linkage.net (pop3.hk.linkage.net [202.76.4.9]) by hub.org (8.9.3/8.9.3) with ESMTP id CAA81052 for ; Thu, 15 Jul 1999 02:19:40 -0400 (EDT) (envelope-from kin.chan@technologist.com) Received: from terence ([210.184.79.157]) by mail.hk.linkage.net (8.8.8/8.8.8) with SMTP id OAA15521 for ; Thu, 15 Jul 1999 14:19:32 +0800 (HKT) From: "Terence Chan" To: Subject: RE: [INTERFACES] ODBC problem Date: Thu, 15 Jul 1999 14:22:41 +0800 Message-ID: <000401bece8a$7235f4e0$9d4fb8d2@terence.cetec.com.hk> MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal In-Reply-To: <378D7C3A.4682B800@trust.ee> Thanks, Yes, the file tblItem is belongs to user postgres. And I have also tried the chmod 777 the file and still can't access it. BTW, I can link / access the file from within MS Access via ODBC. Any idea? -----Original Message----- From: hannu@kodu.home.ee [mailto:hannu@kodu.home.ee] On Behalf Of Hannu Krosing Sent: Thursday, July 15, 1999 2:14 PM To: Terence Chan Cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] ODBC problem Terence Chan wrote: > > I have exported a table from MS Access 97 to PG via ODBC. I can see the file > is exported to the correct place but psql complaining the table is not > there. Are you sure that the file (and directories leading to it) are readable by the user postgres, or whatever your backend runs as ? As a last resort move the file to /tmp and chmod 777 it. ------ Hannu From byronn@solipsys.com Thu Jul 15 13:48:51 1999 Received: from bastion.solipsys.com (bastion.solipsys.com [209.117.190.2]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA51972 for ; Thu, 15 Jul 1999 09:48:51 -0400 (EDT) (envelope-from byronn@solipsys.com) Received: from solipsys.com ([209.117.190.166]) by bastion.solipsys.com (8.9.1a/8.9.1) with ESMTP id JAA04173 for ; Thu, 15 Jul 1999 09:48:21 -0400 (EDT) Message-ID: <378DE6F2.51FDFCFB@solipsys.com> Date: Thu, 15 Jul 1999 09:49:38 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgreSQL.org Subject: [Fwd: [INTERFACES] ODBC problem] Content-Type: multipart/mixed; boundary="------------6D177BB10D505D4B5C10716B" This is a multi-part message in MIME format. --------------6D177BB10D505D4B5C10716B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------6D177BB10D505D4B5C10716B Content-Type: message/rfc822 Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <378DDB56.4E915913@solipsys.com> Date: Thu, 15 Jul 1999 09:00:06 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.51 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Terence Chan Subject: Re: [INTERFACES] ODBC problem References: <000401bece8a$7235f4e0$9d4fb8d2@terence.cetec.com.hk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Terence Chan wrote: > Thanks, > > Yes, the file tblItem is belongs to user postgres. And I have also tried the > chmod 777 the file and still can't access it. > Its because the table is called "tblItem", notice the mixed case. If you want to access this in pg, you need to use quotes around the table name to preserve the case. The odbc does this for you. Byron --------------6D177BB10D505D4B5C10716B-- From ainsogna@hotmail.com Sun Apr 2 07:55:50 2000 Received: from hotmail.com (oe22.law4.hotmail.com [216.33.148.15]) by hub.org (8.9.3/8.9.3) with SMTP id DAA18009 for ; Sun, 2 Apr 2000 03:55:50 -0400 (EDT) (envelope-from ainsogna@hotmail.com) Received: (qmail 11570 invoked by uid 65534); 2 Apr 2000 07:55:19 -0000 Message-ID: <20000402075519.11569.qmail@hotmail.com> X-Originating-IP: [207.231.100.102] From: "Albert J. Insogna" To: Subject: ODBC Problem Date: Sun, 2 Apr 2000 03:57:00 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BF9C57.7F561920" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 X-Archive-Number: 200004/5 This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF9C57.7F561920 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello all, Whenever I try and use ODBC to access my Postgres database through MS A= ccess (or anything else), I am getting "Error #210 - Unsupported Front End = Protocol". Any ideas? Thanks in advance... Al Insogna ------=_NextPart_000_0005_01BF9C57.7F561920 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello all,
    Whenever I try and use = ODBC to=20 access my Postgres database through MS Access (or anything else), I am gett= ing=20 "Error #210 - Unsupported Front End Protocol".  Any ideas?  Thank= s in=20 advance...
Al Insogna
------=_NextPart_000_0005_01BF9C57.7F561920-- From lockhart@alumni.caltech.edu Sun Apr 2 15:26:17 2000 Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA50312 for ; Sun, 2 Apr 2000 11:26:17 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id PAA17195; Sun, 2 Apr 2000 15:37:50 GMT Message-ID: <38E7694E.5504DF1B@alumni.caltech.edu> Date: Sun, 02 Apr 2000 15:37:50 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Albert J. Insogna" CC: pgsql-interfaces@postgresql.org Subject: Re: ODBC Problem References: <20000402075519.11569.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200004/6 > Whenever I try and use ODBC to access my Postgres database > through MS Access (or anything else), I am getting "Error #210 - > Unsupported Front End Protocol". Any ideas? Thanks in advance... You probably have a mismatch between versions. Make sure you are using the latest release of both ODBC and Postgres, or be more specific about which versions you *are* running... - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California From george@calamba.laguna.net Sat Oct 7 09:01:57 2000 Received: from calamba.laguna.net ([210.16.49.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e9791jJ58945 for ; Sat, 7 Oct 2000 05:01:57 -0400 (EDT) Received: from localhost (george@localhost) by calamba.laguna.net (8.9.3/8.9.3) with ESMTP id RAA11623 for ; Sat, 7 Oct 2000 17:02:55 +0800 Date: Sat, 7 Oct 2000 17:02:55 +0800 (PHT) From: "George P. Esperanza" To: pgsql-interfaces@postgresql.org Subject: ODBC problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200010/32 Hi! I'm using postgres 7.0.2 running in Linux. I tried to install Postgres ODBC driver in my Windows95 PC just to test if i can connect to my Postgres database using ODBC. I also downloaded ZEOS database explorer to test if this will work. After configuring User DSN and Zeos Databse Explorer Logon, i got this message: Password Authentication failed for user 'user' I tried other users and still the same problem. My Postgres is already running with -i parameter (compiled with '--with-odbc') and i don't have any problem accessing my database from another linux machine. I checked Postgres log file and it shows the same message. By the way, my Postgres server is configured to "crypt" authentication type. I'm planning to develop VB application that will use Postgres as my database server. Please advise. Thanks George From cedarc@visionforisrael.com Sat Oct 7 13:49:10 2000 Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.org (8.10.1/8.10.1) with ESMTP id e97DnAJ31894 for ; Sat, 7 Oct 2000 09:49:10 -0400 (EDT) Received: from nanu.visionforisrael.com (ras9-p20.jlm.netvision.net.il [62.0.166.20]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id PAA02644; Sat, 7 Oct 2000 15:49:07 +0200 (IST) Received: from localhost (cedarc@localhost) by nanu.visionforisrael.com (8.9.3/8.9.3) with ESMTP id QAA15677; Sat, 7 Oct 2000 16:31:04 +0200 Date: Sat, 7 Oct 2000 16:31:04 +0200 (IST) From: Cedar Cox To: "George P. Esperanza" cc: pgsql-interfaces@postgresql.org Subject: Re: ODBC problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200010/35 > By the way, my Postgres server is configured to "crypt" authentication > type. That's the reason... My understanding is that there is no libcrypt for win32 so the windows ODBC driver doesn't support crypt passwords. Allow passwords in the clear (change 'crypt' to 'password' in pg_hba.conf) and it should work fine. Of course this could be a security hole so be careful what you do. Be sure to limit the IPs that are allowed to connect. Alternatively, you could do something I've thought about but never done myself.. set up a ssh tunnel from the client to the server. I think this can be done. Even if the ODBC driver did support crypt passwords, the sql queries and responses could be picked up just as easily so there wouldn't really be much of a security gain. If you're in an environment where non-crypt passwords are a security risk, then ssh (or some other encryption) is probably the way to go. Thoughts?? -Cedar From tom@sdf.com Mon Oct 9 00:17:49 2000 Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.org (8.10.1/8.10.1) with ESMTP id e990HmJ04906 for ; Sun, 8 Oct 2000 20:17:49 -0400 (EDT) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13iQFs-0005RE-00; Sun, 8 Oct 2000 16:53:20 -0700 Date: Sun, 8 Oct 2000 16:53:04 -0700 (PDT) From: Tom Samplonius To: Cedar Cox cc: "George P. Esperanza" , pgsql-interfaces@postgresql.org Subject: Re: ODBC problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200010/37 On Sat, 7 Oct 2000, Cedar Cox wrote: > > By the way, my Postgres server is configured to "crypt" authentication > > type. > > That's the reason... My understanding is that there is no libcrypt for > win32 so the windows ODBC driver doesn't support crypt passwords. Allow > passwords in the clear (change 'crypt' to 'password' in pg_hba.conf) and > it should work fine. Of course this could be a security hole so be > careful what you do. Be sure to limit the IPs that are allowed to > connect. Except for the fact that crypt provides little if no security increase. Even though only a crypted password is sent over the wire, that crypted password can still be captured off the wire and replayed to get access. Plus crypt is a rather fast algorithm, making it easy to brute-force. Of course, this is all pretty typical for databases. Most databases transmit passwords in the clear. Some try a lame scramble, which is trivial to unscramble and worse than crypt in that it is easy to reverse. Even databases that don't transmit the password in the clear can by easily broken by a replay attack, or if driver source is available, simply patch the driver to accept already encrypted passwords. Tom From sabirsou@caramail.com Mon Oct 9 09:52:03 2000 Received: from mail.caramail.com (mail.caramail.com [195.68.99.70]) by hub.org (8.10.1/8.10.1) with ESMTP id e999q3J42927 for ; Mon, 9 Oct 2000 05:52:03 -0400 (EDT) Date: Mon, 9 Oct 2000 05:52:03 -0400 (EDT) Received: from caramail.com (www19.caramail.com [195.68.99.39]) by mail.caramail.com (8.8.8/8.8.8) with SMTP id LAA10377 for pgsql-interfaces@postgresql.org; Mon, 9 Oct 2000 11:52:48 +0100 (WET DST) Posted-Date: Mon, 9 Oct 2000 11:52:48 +0100 (WET DST) From: soulimane sabir To: pgsql-interfaces@postgresql.org Message-ID: <971088768023011@caramail.com> X-Mailer: Caramail - www.caramail.com X-Originating-IP: [195.127.43.165] Mime-Version: 1.0 Subject: ODBC problem Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200010/39 Dear all Does anyone know how to get the ODBC driver for Lotus approach 3.0 ? I didn't find it in the web. Thanks in advance. Soulimane ______________________________________________________ Bo=EEte aux lettres - Caramail - http://www.caramail.com From peter_e@gmx.net Mon Oct 9 16:31:47 2000 Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by hub.org (8.10.1/8.10.1) with ESMTP id e99GVlJ76014 for ; Mon, 9 Oct 2000 12:31:47 -0400 (EDT) Received: from fmrl01.sul.t-online.de by mailout01.sul.t-online.com with smtp id 13ifmh-0003jH-01; Mon, 09 Oct 2000 18:28:15 +0200 Received: from peter.localdomain (520083510237-0001@[212.185.245.81]) by fmrl01.sul.t-online.com with esmtp id 13ifmZ-18LDfcC; Mon, 9 Oct 2000 18:28:07 +0200 Date: Mon, 9 Oct 2000 18:32:10 +0200 (CEST) From: Peter Eisentraut To: Tom Samplonius cc: Cedar Cox , "George P. Esperanza" , pgsql-interfaces@postgresql.org Subject: Re: ODBC problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 520083510237-0001@t-dialin.net X-Archive-Number: 200010/44 Tom Samplonius writes: > Except for the fact that crypt provides little if no security increase. > Even though only a crypted password is sent over the wire, that crypted > password can still be captured off the wire and replayed to get access. Only if you happen to get the same salt from the server every time, which is rather unlikely. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/ From tgl@sss.pgh.pa.us Mon Oct 9 16:47:36 2000 Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e99GlaJ83033 for ; Mon, 9 Oct 2000 12:47:36 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e99GjbB25672; Mon, 9 Oct 2000 12:45:37 -0400 (EDT) To: Peter Eisentraut cc: Tom Samplonius , Cedar Cox , "George P. Esperanza" , pgsql-interfaces@postgresql.org Subject: Re: ODBC problem In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Mon, 09 Oct 2000 18:32:10 +0200" Date: Mon, 09 Oct 2000 12:45:36 -0400 Message-ID: <25669.971109936@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/45 Peter Eisentraut writes: > Tom Samplonius writes: >> Except for the fact that crypt provides little if no security increase. >> Even though only a crypted password is sent over the wire, that crypted >> password can still be captured off the wire and replayed to get access. > Only if you happen to get the same salt from the server every time, which > is rather unlikely. However, the standard crypt algorithm only has a small number of distinct salt values, so an attacker who's sniffed one login transaction can connect repeatedly until challenged with the same salt he saw used before. We have talked about adding a higher-security login protocol --- you can find past threads about this in the pghackers archive. IIRC a fairly complete design was worked out, but no one's got round to implementing it yet. There might still have been some unresolved objections, too. regards, tom lane From EvilAzrael@EvilAzrael.de Tue Jan 2 22:24:06 2001 Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f02MO6706964 for ; Tue, 2 Jan 2001 17:24:06 -0500 (EST) (envelope-from pgsql-interfaces-owner@postgresql.org) Received: from hermes.altec.group (hermes.altecgroup.gr [212.89.165.3]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f01B3OL59491 for ; Mon, 1 Jan 2001 06:03:29 -0500 (EST) (envelope-from EvilAzrael@EvilAzrael.de) Received: from cyclades.acn.gr ([172.16.10.103]) by hermes.altec.group (Netscape Messaging Server 4.15) with SMTP id G6HDD600.P01 for ; Mon, 1 Jan 2001 13:03:06 +0200 Received: from router.azrael.de ([62.225.229.111]) by cyclades.acn.gr (NAVIEG 2.1 bld 63) with SMTP id M2001010113030427118 ; Mon, 01 Jan 2001 13:03:04 +0200 Received: from EvilAzrael.de (azrael.azrael.de [192.168.202.18]) by router.azrael.de (8.10.2/8.10.2) with ESMTP id f013jlH01047 for ; Mon, 1 Jan 2001 04:45:47 +0100 Message-ID: <3A4FFE60.972A1F1C@EvilAzrael.de> Date: Mon, 01 Jan 2001 04:49:52 +0100 From: Evil Azrael Organization: No Organization - Just Chaos X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: de,en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: ODBC-Problem Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200101/17 X-Sequence-Number: 626 HI I have just moved my old MS Access Database to a postgres database via odbc. all went okay, and i can access the database in MS Access via ODBC. Only a Client programm that i wrote canīt access the database anymore via ODBC. The Visual BAsic Database programm says that the database itself is updateable, but the tables in it arenīt updateable, and all tries to connect to a table in VB via the OpenRecordset method fail with the error message "parse error near [name of the table]" or VB tells that itīs a connection error. Thatīs weird. MS Access has no problems connecting and writing to the database. VBīs Visual Database Manager can connect to the database, but can only read tables. MY VB programm canīt even connect to the tables, but it worked quite good via ODBC to the Access Database. I donīt know what i can anymore, so please help if you know a solution. Christoph Nelles From EvilAzrael@EvilAzrael.de Tue Jan 2 19:08:45 2001 Received: from mail.postgresql.org (webmail.postgresql.org [216.126.85.28]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f02J8jL01525 for ; Tue, 2 Jan 2001 14:08:45 -0500 (EST) (envelope-from pgsql-interfaces-owner@postgresql.org) Received: from router.azrael.de (p3EE1E5E2.dip.t-dialin.net [62.225.229.226]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f026ZxL36986 for ; Tue, 2 Jan 2001 01:35:59 -0500 (EST) (envelope-from EvilAzrael@EvilAzrael.de) Received: from EvilAzrael.de (azrael.azrael.de [192.168.202.18]) by router.azrael.de (8.10.2/8.10.2) with ESMTP id f01CvGH01760 for ; Mon, 1 Jan 2001 13:57:16 +0100 Message-ID: <3A507F8E.E0D3D5B9@EvilAzrael.de> Date: Mon, 01 Jan 2001 14:01:03 +0100 From: Evil Azrael Organization: No Organization - Just Chaos X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: de,en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: Re: ODBC-Problem References: <3A4FFE60.972A1F1C@EvilAzrael.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Archive-Number: 200101/9 X-Sequence-Number: 616 ok, i got a solution myself. i mistyped one tablename and wrote the initial letter lower-case and it worked via odbc, even if i wroted the name uppercase in VB. hm, thatīs strange, should i post this behavior to the bugs-mailinglist or is that behavior okay? Christoph Nelles Evil Azrael wrote: > > HI > > I have just moved my old MS Access Database to a postgres database via > odbc. all went okay, and i can access the database in MS Access via > ODBC. Only a Client programm that i wrote canīt access the database > anymore via ODBC. The Visual BAsic Database programm says that the > database itself is updateable, but the tables in it arenīt updateable, > and all tries to connect to a table in VB via the OpenRecordset method > fail with the error message "parse error near [name of the table]" or VB > tells that itīs a connection error. > Thatīs weird. > MS Access has no problems connecting and writing to the database. > VBīs Visual Database Manager can connect to the database, but can only > read tables. > MY VB programm canīt even connect to the tables, but it worked quite > good via ODBC to the Access Database. > > I donīt know what i can anymore, so please help if you know a solution. > > Christoph Nelles From mdavis@sevainc.com Wed Jan 3 00:53:42 2001 Received: from mail01.phoenixdsl.com (mail.phoenixdsl.com [216.178.151.24]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f030rg720894 for ; Tue, 2 Jan 2001 19:53:42 -0500 (EST) (envelope-from mdavis@sevainc.com) Received: (qmail 46536 invoked by uid 89); 3 Jan 2001 00:54:21 -0000 Received: from unknown (HELO SALLY) (64.32.157.45) by 0 with SMTP; 3 Jan 2001 00:54:21 -0000 Received: by localhost with Microsoft MAPI; Tue, 2 Jan 2001 17:54:20 -0700 Message-ID: <01C074E5.086196C0.mdavis@sevainc.com> From: Michael Davis Reply-To: "mdavis@sevainc.com" To: "pgsql-interfaces@postgresql.org" Subject: RE: ODBC-Problem Date: Tue, 2 Jan 2001 17:54:17 -0700 Organization: Seva Inc. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/21 X-Sequence-Number: 630 Add a primary key index to the tables that you want to be able to update. Access relies on the primary key for a lot of things. I recommend you add a primary key to all postgres tables. -----Original Message----- From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de] Sent: Sunday, December 31, 2000 8:50 PM To: pgsql-interfaces@postgresql.org Subject: ODBC-Problem HI I have just moved my old MS Access Database to a postgres database via odbc. all went okay, and i can access the database in MS Access via ODBC. Only a Client programm that i wrote can?t access the database anymore via ODBC. The Visual BAsic Database programm says that the database itself is updateable, but the tables in it aren?t updateable, and all tries to connect to a table in VB via the OpenRecordset method fail with the error message "parse error near [name of the table]" or VB tells that it?s a connection error. That?s weird. MS Access has no problems connecting and writing to the database. VB?s Visual Database Manager can connect to the database, but can only read tables. MY VB programm can?t even connect to the tables, but it worked quite good via ODBC to the Access Database. I don?t know what i can anymore, so please help if you know a solution. Christoph Nelles From aalang@rutgersinsurance.com Wed Jan 3 13:59:20 2001 Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f03DxK782910 for ; Wed, 3 Jan 2001 08:59:20 -0500 (EST) (envelope-from aalang@rutgersinsurance.com) Received: from 6014cwpza006 ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id JAA30809 for ; Wed, 3 Jan 2001 09:04:02 -0500 Message-ID: <006e01c0758d$af569720$330a0a0a@6014cwpza006> From: "Adam Lang" To: References: <01C074E5.086196C0.mdavis@sevainc.com> Subject: Re: RE: ODBC-Problem Date: Wed, 3 Jan 2001 09:01:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200101/29 X-Sequence-Number: 638 Also, make sure the ODBC driver for postgres is set for updating. By default it is read only. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Michael Davis" To: Sent: Tuesday, January 02, 2001 7:54 PM Subject: [INTERFACES] RE: ODBC-Problem > Add a primary key index to the tables that you want to be able to update. > Access relies on the primary key for a lot of things. I recommend you add > a primary key to all postgres tables. > > -----Original Message----- > From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de] > Sent: Sunday, December 31, 2000 8:50 PM > To: pgsql-interfaces@postgresql.org > Subject: ODBC-Problem > > HI > > I have just moved my old MS Access Database to a postgres database via > odbc. all went okay, and i can access the database in MS Access via > ODBC. Only a Client programm that i wrote can?t access the database > anymore via ODBC. The Visual BAsic Database programm says that the > database itself is updateable, but the tables in it aren?t updateable, > and all tries to connect to a table in VB via the OpenRecordset method > fail with the error message "parse error near [name of the table]" or VB > tells that it?s a connection error. > That?s weird. > MS Access has no problems connecting and writing to the database. > VB?s Visual Database Manager can connect to the database, but can only > read tables. > MY VB programm can?t even connect to the tables, but it worked quite > good via ODBC to the Access Database. > > > I don?t know what i can anymore, so please help if you know a solution. > > > Christoph Nelles From mdavis@sevainc.com Wed Jan 3 16:05:27 2001 Received: from mail01.phoenixdsl.com (mail.phoenixdsl.com [216.178.151.24]) by mail.postgresql.org (8.11.1/8.11.1) with SMTP id f03G5Q795050 for ; Wed, 3 Jan 2001 11:05:27 -0500 (EST) (envelope-from mdavis@sevainc.com) Received: (qmail 82358 invoked by uid 89); 3 Jan 2001 16:06:01 -0000 Received: from unknown (HELO SALLY) (64.32.157.45) by 0 with SMTP; 3 Jan 2001 16:06:01 -0000 Received: by localhost with Microsoft MAPI; Wed, 3 Jan 2001 09:06:00 -0700 Message-ID: <01C07564.6461E310.mdavis@sevainc.com> From: Michael Davis Reply-To: "mdavis@sevainc.com" To: "'Evil Azrael'" , "'pgsql-interfaces@postgresql.org'" Subject: RE: ODBC-Problem Date: Wed, 3 Jan 2001 09:05:57 -0700 Organization: Seva Inc. X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Archive-Number: 200101/33 X-Sequence-Number: 642 This sounds strange. I can connect to many tables in less than a minute. I can open tables in seconds regardless of how many rows are in the tables. Access usually only selects 20-30 rows at a time. My ODBC connections to PostgreSQL in Access are fast. Not as fast as opening local Access tables by much faster than 1 minute. You can try different options in your connect statement. Some options work with ODBC, others don't. If this does not help, you will have to email me your VBA code. -----Original Message----- From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de] Sent: Wednesday, January 03, 2001 1:44 AM To: mdavis@sevainc.com Subject: Re: ODBC-Problem thanx for the answer. i have in every table a primary index called ID, but ODBC and VB don?t accept it as a primary keys. and the performance of the OBDC connection is rather bad. he needs almost 1 minute to connect to a table with 300k rows, for just appending a few lines. even sql calls fails. i postponed the whole transfer for a time and check it then again. but thanx for the reply Christoph Nelles Michael Davis wrote: > > Add a primary key index to the tables that you want to be able to update. > Access relies on the primary key for a lot of things. I recommend you add > a primary key to all postgres tables. > > -----Original Message----- > From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de] > Sent: Sunday, December 31, 2000 8:50 PM > To: pgsql-interfaces@postgresql.org > Subject: ODBC-Problem > > HI > > I have just moved my old MS Access Database to a postgres database via > odbc. all went okay, and i can access the database in MS Access via > ODBC. Only a Client programm that i wrote can?t access the database > anymore via ODBC. The Visual BAsic Database programm says that the > database itself is updateable, but the tables in it aren?t updateable, > and all tries to connect to a table in VB via the OpenRecordset method > fail with the error message "parse error near [name of the table]" or VB > tells that it?s a connection error. > That?s weird. > MS Access has no problems connecting and writing to the database. > VB?s Visual Database Manager can connect to the database, but can only > read tables. > MY VB programm can?t even connect to the tables, but it worked quite > good via ODBC to the Access Database. > > I don?t know what i can anymore, so please help if you know a solution. > > Christoph Nelles From simon-emmanuel.rivas@isr.thomson-csf.com Mon Jun 11 13:34:24 2001 Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f5BDYOE78877 for ; Mon, 11 Jun 2001 09:34:24 -0400 (EDT) (envelope-from pgsql-interfaces-owner@postgresql.org) Received: from gwsmtp.thomson-csf.com (gwsmtp.thomson-csf.com [195.101.39.226]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5786ME79705 for ; Thu, 7 Jun 2001 04:06:24 -0400 (EDT) (envelope-from simon-emmanuel.rivas@isr.thomson-csf.com) Received: from thomplex.thomson-csf.com (200.3.2.2) by gwsmtp.thomson-csf.com (NPlex 5.1.053) id 3B1E908C00006A3C for pgsql-interfaces@postgresql.org; Thu, 7 Jun 2001 10:11:23 +0200 Received: from thomplex.thomson-csf.com (200.3.2.2) by thomplex.thomson-csf.com (NPlex 5.1.053) id 3B1C6AF20003F7AA for pgsql-interfaces@postgresql.org; Thu, 7 Jun 2001 10:06:06 +0200 Received: from isr.thomson-csf.com (172.18.61.24) by isrplex.isr.thomson-csf.com (NPlex 5.1.053) id 3B0A25250000ECD5 for pgsql-interfaces@postgresql.org; Thu, 7 Jun 2001 10:06:05 +0200 Message-ID: <3B1F3638.79D8E4B8@isr.thomson-csf.com> Date: Thu, 07 Jun 2001 10:07:20 +0200 From: Simon Emmanuel Rivas Organization: ISR X-Mailer: Mozilla 4.75 [fr] (X11; U; Linux 2.2.17-21mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: ODBC problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200106/43 X-Sequence-Number: 1705 Hi! I have a problem using the ODBC interface. The problem is quite simple: I have created a table with only one field, as follows: create table test (key numeric(1)); Very simple, right? The problem is that, when I look at this table through a client program which runs under Windows (postgres runs under Linux), the field "key" seems to be declared as numeric(3). Does the problem come from ODBC or the client program? Thanx for your help! PS: the client program is Data Factory from Quest Software. I use Postgres 7.1.1 and the ODBC driver is v7.01.0005. From Inoue@tpf.co.jp Tue Jun 12 02:27:14 2001 Received: from sd.tpf.co.jp (sd.tpf.co.jp [210.161.239.34]) by postgresql.org (8.11.3/8.11.1) with SMTP id f5C2REE89636 for ; Mon, 11 Jun 2001 22:27:14 -0400 (EDT) (envelope-from Inoue@tpf.co.jp) Received: (qmail 18468 invoked from network); 12 Jun 2001 02:27:08 -0000 Received: from unknown (HELO viscomail.tpf.co.jp) (100.0.0.108) by sd2.10.0.100.in-addr.arpa with SMTP; 12 Jun 2001 02:27:08 -0000 Received: from tpf.co.jp ([126.0.1.68]) by viscomail.tpf.co.jp (8.8.8+Sun/8.8.8) with ESMTP id LAA23235; Tue, 12 Jun 2001 11:27:01 +0900 (JST) Message-ID: <3B257E30.8171C119@tpf.co.jp> Date: Tue, 12 Jun 2001 11:28:00 +0900 From: Hiroshi Inoue X-Mailer: Mozilla 4.73 [ja] (Windows NT 5.0; U) X-Accept-Language: ja MIME-Version: 1.0 To: Simon Emmanuel Rivas CC: pgsql-interfaces@postgresql.org Subject: Re: ODBC problem References: <3B1F3638.79D8E4B8@isr.thomson-csf.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit X-Archive-Number: 200106/49 X-Sequence-Number: 1712 Simon Emmanuel Rivas wrote: > > Hi! > > I have a problem using the ODBC interface. The problem is quite simple: > I have created a table with only one field, as follows: > create table test (key numeric(1)); > Very simple, right? The problem is that, when I look at this table > through a client program which runs under Windows (postgres runs under > Linux), the field "key" seems to be declared as numeric(3). > Does the problem come from ODBC or the client program? The problem seems to come from the client program. For example, M$ Access recognizes numeric(1). regards, Hiroshi Inoue From jamzb@airnet.com.au Mon Jul 23 12:40:15 2001 Received: from postgresql.org.org (webmail.postgresql.org [216.126.85.28]) by postgresql.org (8.11.3/8.11.1) with SMTP id f6NCeFf30233 for ; Mon, 23 Jul 2001 08:40:15 -0400 (EDT) (envelope-from pgsql-interfaces-owner@postgresql.org) Received: from exchange01.airnet.com.au (apathy.tristesse.org [203.34.190.136]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6I004a49379 for ; Tue, 17 Jul 2001 20:00:04 -0400 (EDT) (envelope-from jamzb@airnet.com.au) Received: by exchange01.office.adl.airnet.com.au with Internet Mail Service (5.5.2650.21) id ; Wed, 18 Jul 2001 09:28:21 +0930 Message-ID: <9CA159BC716ED4119907009027F658330303AB@exchange01.office.adl.airnet.com.au> From: jamzb@airnet.com.au To: pgsql-interfaces@postgresql.org Subject: ODBC Problem Date: Wed, 18 Jul 2001 09:28:20 +0930 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=MD5; boundary="----=_NextPart_000_0035_01C10F6B.FE0FA500" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 X-Archive-Number: 200107/91 X-Sequence-Number: 1845 This is a multi-part message in MIME format. ------=_NextPart_000_0035_01C10F6B.FE0FA500 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0036_01C10F6B.FE15BF80" ------=_NextPart_001_0036_01C10F6B.FE15BF80 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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;F A KEOIDINDEX=0;SHOWOIDCOLUMN=0;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETT INGS=' 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 :-( 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_001_0036_01C10F6B.FE15BF80 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 mac= hine returns empty recordsets.  I made sure all the drivers were t= he 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 d= ata

WinXP B= eta2: okay – queries return data

WinNT4 Server: only queries on some tables return data

Win2k Server SP2: only queries on some tables return dat= a

 

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

 

I looked at the ODBC logs to find something that was fai= ling and couldn’t really see any thing bad:

 

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

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

KEOIDINDEX=3D0;SHOWOIDCOLUMN=3D0;ROWVERSIONING=3D0;SHOWSYSTEMTABLES= =3D0;CONNSETTINGS=3D'

conn=3D35795448, query=3D'SELECT * FROM userservices WHERE printform=3Dtrue AND formpr

inted IS NULL'

    [ = fetched 1 rows ]

conn=3D35795448, SQLDisconnect

 

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

 

I believe the server is running Pos= tgres 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 COPYRIGH= T 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 co= mbo please let me know and I will have a case to get the admin to upgrade.=

 

Cheers & TIA,

    =         Jamz.

 

 

 

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

"We should have laser guns!"

     &= nbsp;- Andrew Hill (Post Support Call)

 

------=_NextPart_001_0036_01C10F6B.FE15BF80-- ------=_NextPart_000_0035_01C10F6B.FE0FA500 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExDjAMBggqhkiG9w0CBQUAMIAGCSqGSIb3 DQEHAQAAoIIKCzCCAj0wggGmAhEAzbp/VvDf5LxU/iKss3KqVTANBgkqhkiG 9w0BAQIFADBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIElu Yy4xNzA1BgNVBAsTLkNsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNh dGlvbiBBdXRob3JpdHkwHhcNOTYwMTI5MDAwMDAwWhcNMjgwODAxMjM1OTU5 WjBfMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNzA1 BgNVBAsTLkNsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAOUZv22jVmEt mUhx9mfeuY3rt56GgAqRDvo4Ja9GiILlc6igmyRdDR/MZW4MsNBWhBiHmgab EKFz37RYOWtuwfYV1aioP6oSBo0xrH+wNNePNGeICc0UEeJORVZpH3gCgNrc R5EpuzbJY1zF4Ncth3uhtzKwezC6Ki8xqu6jZ9rbAgMBAAEwDQYJKoZIhvcN AQECBQADgYEATD+4i8Zo3+5DMw5d6abLB4RNejP/khv0Nq3YlSI2aBFsfELM 85wuxAc/FLAPT/+Qknb54rxK6Y/NoIAK98Up8YIiXbix3YEjo3slFUYweRb4 6gVLlH8dwhzI47f0EEA8E8NfH1PoSOSGtHuhNbB7Jbq4046rPzidADQAmPPR cZQwggNiMIICy6ADAgECAhAL2gsXwT+JjqsJdHq0zi4zMA0GCSqGSIb3DQEB AgUAMF8xCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE3 MDUGA1UECxMuQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0aW9u IEF1dGhvcml0eTAeFw05ODA1MTIwMDAwMDBaFw0wODA1MTIyMzU5NTlaMIHM MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24g VHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBv c2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYG A1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmli ZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMIGfMA0GCSqGSIb3DQEBAQUAA4GN ADCBiQKBgQC7WkSKBBa7Vf0DeootlE8VeDa4DUqyb5xUv7zodyqdufBou5XZ MUFweoFLuUgTVi3HCOGEQqvAopKrRFyqQvCCDgLpL/vCO7u+yScKXbawNkIz tW5UiE+HSr8Z2vkV6A+HthzjzMaajn9qJJLj/OBluqexfu/J2zdqyErICQbk mQIDAQABo4GwMIGtMA8GA1UdEwQIMAYBAf8CAQAwRwYDVR0gBEAwPjA8Bgtg hkgBhvhFAQcBATAtMCsGCCsGAQUFBwIBFh93d3cudmVyaXNpZ24uY29tL3Jl cG9zaXRvcnkvUlBBMDEGA1UdHwQqMCgwJqAkoCKGIGh0dHA6Ly9jcmwudmVy aXNpZ24uY29tL3BjYTEuY3JsMAsGA1UdDwQEAwIBBjARBglghkgBhvhCAQEE BAMCAQYwDQYJKoZIhvcNAQECBQADgYEAAn2eb0VLOKC43ulTZCG85Ewrjx7+ kkCs2Ao5aqEyISwHm6tZ/tJiGn1VOLA3c9z0B2ZjYr3hU3BSh+eo2FLpWy2q 4d7PrDFU1IsZyNgjqO8EKzJ9LBgcyHyJqC538kTRZQpNdLXu0xuSc3QuiTs1 E3LnQDGa07LEq+dWvovj+xUwggRgMIIDyaADAgECAhAbTpFF1fGWXtxZNG7Q qKjoMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5j LjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9 d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJl Zi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBD QSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVk MB4XDTAxMDYzMDAwMDAwMFoXDTAxMDgyOTIzNTk1OVowggEEMRcwFQYDVQQK Ew5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0 d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQ QSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVy c29uYSBOb3QgVmFsaWRhdGVkMScwJQYDVQQLEx5EaWdpdGFsIElEIENsYXNz IDEgLSBNaWNyb3NvZnQxEzARBgNVBAMUCkphbXogQm9tYW4xIjAgBgkqhkiG 9w0BCQEWE2phbXpiQGFpcm5ldC5jb20uYXUwgZ8wDQYJKoZIhvcNAQEBBQAD gY0AMIGJAoGBAKuiOxuI83qQXczco7tm4ejbCPKiMBRKe1ZmE3plrWMiu4SW 15hqhEUIOVJ4t2LW+G1sV7rGC8DdGtT3WRUSoxoZ2IDW5GxtwKhijwmYYxar oig16rUhLxY4K/yDr31B33q/jBC3F1n7xrnCICaBv+DX4hOAFlb1vmBs4Uch vznTAgMBAAGjggEGMIIBAjAJBgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4G C2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJp c2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNpZ24sIEluYy4w AwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwMwYD VR0fBCwwKjAooCagJIYiaHR0cDovL2NybC52ZXJpc2lnbi5jb20vY2xhc3Mx LmNybDANBgkqhkiG9w0BAQQFAAOBgQAs/PJsrKEj8j3QGa3DOaeQBnwiWTS0 Jq5pmmBmgX7NpXgtKrHo376xlfOlrDxcSwn+0ONq2wM2yjhu8cevbPpZ5Vk6 OiDsZZ8wDuxnmMU+N/dcGymirk2N4lrXWQgMyVaQWOBvInHJbbGiw+NNyxq5 J5jdmn1SEBgmSRu2TphaezGCBIswggSHAgEBMIHhMIHMMRcwFQYDVQQKEw5W ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y azFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJ bmNvcnAuIEJ5IFJlZi4sTElBQi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNp Z24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1YnNjcmliZXItUGVyc29uYSBO b3QgVmFsaWRhdGVkAhAbTpFF1fGWXtxZNG7QqKjoMAwGCCqGSIb3DQIFBQCg ggL8MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTAxMDcxNzIzNTgyNFowHwYJKoZIhvcNAQkEMRIEEA41pMSvhwPbQyWUNSc+ rLEwTAYLKoZIhvcNAQkQAgExPTA7BB0AAAAAEAAAAL+eYlMMe9URmSwAkCf2 JhEBAAAAAIABADAXMBWBE2phbXpiQGFpcm5ldC5jb20uYXUwZwYJKoZIhvcN AQkPMVowWDAKBggqhkiG9w0DBzAKBggqhkiG9w0CBTAOBggqhkiG9w0DAgIC AIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwBwYF Kw4DAhowgfIGCSsGAQQBgjcQBDGB5DCB4TCBzDEXMBUGA1UEChMOVmVyaVNp Z24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxRjBE BgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5jb3Jw LiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENs YXNzIDEgQ0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZh bGlkYXRlZAIQG06RRdXxll7cWTRu0Kio6DCB9AYLKoZIhvcNAQkQAgsxgeSg geEwgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4 MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vi c2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEBtOkUXV8ZZe3Fk0btCo qOgwDQYJKoZIhvcNAQEBBQAEgYChsJrYeVjI3Rv7LlzghaEBrAZcmhYhaPgO yhyYfV3dzDMqFv/UwwxYvQcfkYbq8PToZpcH+UuVCF0ETmORd8rTkrOQNmBq lqZEWSI2x7w+paDPcSS+NtUCUrtQFJ6/TIF+gY9GSypWJkHbI30r850J1Tdw qLE5g/6iMkytOIQegAAAAAAAAA== ------=_NextPart_000_0035_01C10F6B.FE0FA500-- From Jamz@AirNet.Com.AU Wed Jul 18 00:12:03 2001 Received: from exchange01.airnet.com.au (apathy.tristesse.org [203.34.190.136]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6I0C3a52604 for ; Tue, 17 Jul 2001 20:12:03 -0400 (EDT) (envelope-from Jamz@AirNet.Com.AU) Received: by exchange01.office.adl.airnet.com.au with Internet Mail Service (5.5.2650.21) id ; Wed, 18 Jul 2001 09:40:32 +0930 Message-ID: <9CA159BC716ED4119907009027F658330303AD@exchange01.office.adl.airnet.com.au> From: Jamz@AirNet.Com.AU To: pgsql-interfaces@postgresql.org Subject: ODBC Problem Date: Wed, 18 Jul 2001 09:40:31 +0930 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C10F1E.0EE9BA9E" X-Archive-Number: 200107/71 X-Sequence-Number: 1825 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C10F1E.0EE9BA9E Content-Type: text/plain 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 :-( 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_001_01C10F1E.0EE9BA9E Content-Type: text/html Content-Transfer-Encoding: quoted-printable

Greetings people,

    =         Before I go nuts, I wonder if anyone has solved this problem before; I have been u= sing the ODBC driver for our Postgres server to deve= lop 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 mac= hine returns empty recordsets.  I made sure all the drivers were t= he 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 B= eta2: okay - queries return data

WinNT4 Server: only queries on some tables return data

Win2k Server SP2: only queries on some tables return dat= a

 

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

 

I looked at the ODBC logs to find something that was fai= ling and couldn't really see any thing bad:

 

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

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

KEOIDINDEX=3D0;SHOWOIDCOLUMN=3D0;ROWVERSIONING=3D0;SHOWSYSTEMTABLES= =3D0;CONNSETTINGS=3D'

conn=3D35795448, query=3D'SELECT * FROM userservices WHERE printform=3Dtrue AND formpr

inted IS NULL'

    [ = fetched 1 rows ]

conn=3D35795448, SQLDisconnect

 

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

 

I believe the server is running Pos= tgres 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 COPYRIGH= T 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 co= mbo please let me know and I will have a case to get the admin to upgrade.=

 

Cheers & TIA,

    =         Jamz.

 

 

 

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

"We should have laser guns!"

     &= nbsp;- Andrew Hill (Post Support Call)

 

------_=_NextPart_001_01C10F1E.0EE9BA9E-- From SHenshall@westcountrypublications.co.uk Wed Jul 18 08:54:22 2001 Received: from mail_exchange.westcountrypublications.co.uk ([195.171.163.135]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6I8sLa73085 for ; Wed, 18 Jul 2001 04:54:22 -0400 (EDT) (envelope-from SHenshall@westcountrypublications.co.uk) Received: by MAIL_EXCHANGE with Internet Mail Service (5.5.2650.21) id ; Wed, 18 Jul 2001 09:58:18 +0100 Message-ID: From: "Henshall, Stuart - WCP" To: "'Jamz@AirNet.Com.AU'" , pgsql-interfaces@postgresql.org Subject: RE: ODBC Problem Date: Wed, 18 Jul 2001 09:58:17 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Archive-Number: 200107/72 X-Sequence-Number: 1826 It may well be worth trying the latest version of the driver (Have a look at http://odbc.postgresql.org , or http://www.ca.postgresql.org/ftpsite/odbc/versions/full/) Also there is an postgreSQL ODBC specific list: pgsql-odbc@postgresql.org - Stuart > -----Original Message----- > From: Jamz@AirNet.Com.AU [SMTP:Jamz@AirNet.Com.AU] > Sent: Wednesday, July 18, 2001 1:11 AM > To: pgsql-interfaces@postgresql.org > Subject: 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;CONNSETTIN > GS=' > 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 :-( > > 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) > From ltibor@mail.tiszanet.hu Wed Jul 18 10:32:30 2001 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-- From SHenshall@westcountrypublications.co.uk Tue Jul 24 09:00:11 2001 Received: from mail_exchange.westcountrypublications.co.uk ([195.171.163.135]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6O907f91380 for ; Tue, 24 Jul 2001 05:00:11 -0400 (EDT) (envelope-from SHenshall@westcountrypublications.co.uk) Received: by MAIL_EXCHANGE with Internet Mail Service (5.5.2650.21) id ; Tue, 24 Jul 2001 10:04:02 +0100 Message-ID: From: "Henshall, Stuart - WCP" To: "'jamzb@airnet.com.au'" , pgsql-interfaces@postgresql.org Subject: RE: ODBC Problem Date: Tue, 24 Jul 2001 10:04:01 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Archive-Number: 200107/98 X-Sequence-Number: 1852 Hello, the PostgreSQL ODBC driver is up to 7.01.0006 now. Try this out. It is available on odbc.postgresql.org. (It may also be worth looking at the archives of the pgsql-odbc mailing list or on techdocs.postgresql.org). - Stuart > -----Original Message----- > From: jamzb@airnet.com.au [SMTP:jamzb@airnet.com.au] > Sent: Wednesday, July 18, 2001 12:58 AM > To: pgsql-interfaces@postgresql.org > Subject: 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;CONNSETTIN > GS=' > 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 :-( > > 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) >