Received: from u1.abs.net (root@u1.abs.net [207.114.0.131])
	by hub.org (8.9.2/8.9.1) with ESMTP id RAA65983
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 1 Feb 1999 17:42:33 -0500 (EST)
	(envelope-from byronn@insightdist.com)
Received: from insightdist.com (nobody@localhost)
	by u1.abs.net (8.9.0/8.9.0) with UUCP id RAA15054
	for pgsql-interfaces@postgreSQL.org;
	Mon, 1 Feb 1999 17:20:26 -0500 (EST)
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 AA05097; Mon, 1 Feb 1999 17:05:01 -0500
Received: from byronn by ceodev (AIX 4.1/UCB 5.64/4.03)
	id AA22620; Mon, 1 Feb 1999 17:05:00 -0500
Message-Id: <36B62572.422382EF@insightdist.com>
Date: Mon, 01 Feb 1999 17:06:42 -0500
From: Byron Nikolaidis <byronn@insightdist.com>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
Mime-Version: 1.0
To: Valerio Santinelli <tanis@mediacom.it>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] ODBC Locking troubles
References: <36B5B363.D8082D12@mediacom.it>
 <36B5B93A.3B295B77@insightdist.com>
	<36B63FE9.4047B56E@mediacom.it>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Valerio Santinelli wrote:

> Byron Nikolaidis wrote:
>
> > > I'm still messing around with MSAccess as interface for my PostgreSQL
> > > database and I've found out something interesting.
> > >
> > > When trying to access some data to update in a simple table (just a
> > > serial and 4 columns of various types) I noticed that when I try to do
> > > an update on any of the records from a form or directly from the table,
> > > MSAccess is saying that another user is locking that record and cannot
> > > update it. Obviously that's not true since that's the only task
> > > accessing the database right now.
> > >
> >
> > Check the "Use Declare/Fetch" option under the odbc driver options (Advanced
> > Options/Driver).  If it is enabled, turn it off.  Until we have the MVCC
> > locking, there is always a potential for problems with this option enabled.
> >
>
> I checked it out and it's already turned off on both PCs.
>
> > > Now I'm thinking it's an ODBC problem and I should update some drivers
> > > on my work's machine but I already tried installing the new DAO and ODBC
> > > stuff from Visual Studio 6 Suite but nothing changed. Any idea ? Anybody
> > > happened to notice this strange behaviour ?
> > >
> >
> > It never hurts to make sure you have the latest odbc driver
> > (http://www.insightdist.com/psqlodbc).
> >
>
> Done this, too :)
> Same driver on both machines.
>
> --
>
> C'ya!
>
> Valerio Santinelli a.k.a. TANiS
> [tanis@mediacom.it]+:+[http://www.mediacom.it/~tanis]


Please send me the commlog file ("psqlodbc.log") of the session.  You may have to
enable this feature on the driver options.

Byron