RE: ODBC and Access 2000

I did not see these in the earlier messages, but I may have missed so
forgive me and ignore this message if so...

Do you have "Recognise Unique Indexes" checked in the ODBC driver?
Do you have the MS Access key icon next to the primary key in the design
view of the table? You can look at the design view even though Access gives
message saying you can't change it (resonably enough)
When you link the table do you get a pop-up asking you to nominate a unique
column? If you do it means that Access has not found the key.

Also, by the way, if you make any changes to the table design on the
backend, you need to delete the table link in Access and relink it. I don't
thing the link-refeshing add-in refeshes well enough. Not doing this can
give rise to confusing problem-solving sessions.

----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org]On Behalf Of Chris Gray
Sent: 09 May 2001 15:07
To: Peter Wilkinson; Hiroshi Inoue; Jean-Michel POURE; Keith Todd
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: RE: [ODBC] ODBC and Access 2000

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
>

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly