Received: from s20.highertech.net (root@s20.highertech.net [209.54.120.20]) by hub.org (8.9.3/8.9.3) with ESMTP id RAA12550 for ; Wed, 30 Jun 1999 17:39:46 -0400 (EDT) (envelope-from jt-kirkpatrick@mpsllc.com) Received: from kirkpatrickjt (whiteoak-34.highertech.net [209.140.56.34] (may be forged)) by s20.highertech.net (8.8.6/8.8.6) with SMTP id RAA29727 for ; Wed, 30 Jun 1999 17:39:05 -0400 Received: by localhost with Microsoft MAPI; Wed, 30 Jun 1999 17:40:31 -0400 Message-ID: <01BEC31F.A61BE100.jt-kirkpatrick@mpsllc.com> From: JT Kirkpatrick To: "'pgsql-interfaces@hub.org'" Subject: odbc timeout! Date: Wed, 30 Jun 1999 17:40:30 -0400 Organization: MPS, LLC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 12 TEXT we are using access97 linking to postgres 6.4.2 through the most recent odbc driver. in my access queries i have the odbc driver timeout set to 60 seconds. normally this isn't a problem; however, i just ran an ugly query from the console that did cause most clients to timeout. that is when i realized that when it time-outs, access ceases to respond to its operating system -- you have to do the dreaded ctrl alt del and end-task. is this something the odbc driver could prevent, or is this an access97 fault?? jt