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 f03GBj795694 for ; Wed, 3 Jan 2001 11:11:45 -0500 (EST) (envelope-from mdavis@sevainc.com) Received: (qmail 15306 invoked by uid 89); 3 Jan 2001 16:12:19 -0000 Received: from unknown (HELO SALLY) (64.32.157.45) by 0 with SMTP; 3 Jan 2001 16:12:19 -0000 Received: by localhost with Microsoft MAPI; Wed, 3 Jan 2001 09:12:17 -0700 Message-ID: <01C07565.452D3070.mdavis@sevainc.com> From: Michael Davis Reply-To: "mdavis@sevainc.com" To: "'Cedar Cox'" , "pgsql-interfaces@postgresql.org" Subject: RE: ODBC - Invalid protocol character Date: Wed, 3 Jan 2001 09:12:14 -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/34 X-Sequence-Number: 643 Does this query work in psql? Can we see the psqlodbc_????.log file from your C: drive? -----Original Message----- From: Cedar Cox [SMTP:cedarc@visionforisrael.com] Sent: Wednesday, January 03, 2001 6:51 AM To: pgsql-interfaces@postgresql.org Subject: ODBC - Invalid protocol character When using the odbc driver from Access in Win9x we sometimes receive the error message "An invalid protocol character was received from the backend". While this could mean that someone passed gas, I don't think so. Anyone see this before? The one particular query that gave this error is: SELECT Description AS "Item", SuitabilityName AS "Suitability", AgeGroupName AS "Age Group", SizeName AS "Size", Qty AS "Quantity", tblStResTree_cache.SurID FROM tblListRequestItems, tblIdSuitability, tblIdAgeGroup, tblIdSize, tblStResTree_cache WHERE tblListRequestItems.SuitabilityID = tblIdSuitability.SuitabilityID AND tblListRequestItems.AgeGroupID = tblIdAgeGroup.AgeGroupID AND tblListRequestItems.SizeID = tblIdSize.SizeID AND tblListRequestItems.TreeID = tblStResTree_cache.TreeID AND RequestItemID=3; It really doesn't look strange at all, so I'm not sure what's wrong. This happened a while ago and things have changed since then so I'm not sure if I can reproduce the error or not. If needed I can dig through my archive in a little and try to give a stable test case for this problem. -Cedar