Skip site navigation (1) Skip section navigation (2)

RE: ODBC and Access 2000

From: Chris Gray <cpgray(at)library(dot)uwaterloo(dot)ca>
To: Peter Wilkinson <peterw(at)innate(dot)co(dot)uk>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr>, Keith Todd <ktodd(at)spiritone(dot)com>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: RE: ODBC and Access 2000
Date: 2001-05-09 14:06:55
Message-ID: Pine.SOL.4.21.0105091005070.3942-100000@library.uwaterloo.ca (view raw or flat)
Thread:
Lists: pgsql-odbc
Still no luck.  I tried making all fields non null and supplying a default
value and still get the same error message.

Chris


On Tue, 8 May 2001, Chris Gray wrote:

> Thanks to everyone who replied.
> 
> To answer Hiroshi Inoue:
> I am running the 7.01.00.05 version of pgsqlodbc which I downloaded just
> last week.
> 
> To answer Peter Wilkinson:
> The table that I can't update via Access has no boolean fields in it.  But
> I'll try ensuring that all fields have a default.
> 
> To answer Jean-Michel POURE: I have MDAC 2.6 which I downloaded last week
> when installing pgAdmin.  The Jet upgrade you pointed me to was for
> Jet 4.0 SP 3.  I ran this upgrade but it doesn't seem to change the
> behavior.  And thanks for the FAQ tip.
> 
> Chris
> 
> On Tue, 8 May 2001, Peter Wilkinson wrote:
> 
> > We had this problem and tracked it down to the differences between Access's
> > and Posgres's handling of uninitialised booleans.  The solution was to add
> > "set default false" on any booleans. Access does not set a default on
> > booleans in new rows it creates, but expects them to be not-null.
> > 
> > By the way, "write conflict" seems to be Access's message of last resort:
> > read it as meaning "something has gone wrong and I don't know what".
> > 
> > Peter Wilkinson
> > Innate Management Systems Ltd
> > 
> > -----Original Message-----
> > From: pgsql-odbc-owner(at)postgresql(dot)org
> > [mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Hiroshi Inoue
> > Sent: 08 May 2001 01:19
> > To: Chris Gray
> > Cc: pgsql-odbc(at)postgresql(dot)org
> > Subject: Re: [ODBC] ODBC and Access 2000
> > 
> > 
> > Chris Gray wrote:
> > >
> > > I'm running PostgreSQL on a Debian GNU/Linux box and have installed
> > > pgAdmin successfully on a Windows 98 machine.  pgAdmin works fine for
> > > updating tables.  I can use Access 2000 to insert a new row in a table.
> > > If I create an Access SQL query to update or delete a row, it works.
> > >
> > > If I try to delete or update a row using the data sheet view of a linked
> > > table I get a "write conflict" error or a message from the Jet db engine
> > > that another user is trying to modify the same data even though I'm the
> > > only one connected to the database.
> > >
> > > Any idea what's going on and how to stop it?
> > >
> > 
> > Which version of psqlodbc driver are you using ?
> > If it's older than 7.01.0003 please try the latest one.
> > 
> > regards,
> > Hiroshi Inoue
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
> > 
> > 
> > ---------------------------(end of broadcast)---------------------------
> > TIP 2: you can get off all lists at once with the unregister command
> >     (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
> > 
> 
> 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
> 



In response to

Responses

pgsql-odbc by date

Next:From: Peter WilkinsonDate: 2001-05-09 14:57:49
Subject: RE: ODBC and Access 2000
Previous:From: Chris GrayDate: 2001-05-09 13:20:09
Subject: Re: Re: ODBC and Access 2000

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group