Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f03GjK798176
	for <pgsql-interfaces@postgresql.org>;
	Wed, 3 Jan 2001 11:45:20 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f03GjsB16473;
	Wed, 3 Jan 2001 11:45:54 -0500 (EST)
To: Cedar Cox <cedarc@visionforisrael.com>
cc: pgsql-interfaces@postgresql.org
Subject: Re: ODBC - Invalid protocol character 
In-reply-to: 
 <Pine.LNX.4.21.0101031537070.31552-100000@nanu.visionforisrael.com>
References: 
 <Pine.LNX.4.21.0101031537070.31552-100000@nanu.visionforisrael.com>
Comments: In-reply-to Cedar Cox <cedarc@visionforisrael.com>
	message dated "Wed, 03 Jan 2001 15:51:20 +0200"
Date: Wed, 03 Jan 2001 11:45:54 -0500
Message-ID: <16470.978540354@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200101/35
X-Sequence-Number: 644

Cedar Cox <cedarc@visionforisrael.com> writes:
> 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?

That suggests that the frontend and backend got out of sync.  There used
to be some bugs that could cause that, but I thought we'd fixed 'em all.
What Postgres version are you running?

If you're on 7.0 or later, I'd definitely like to see a reproducible
test case...

			regards, tom lane