But then a funny thing happened. When I refreshed the view, the records changed from "#Deleted" to all the data I put in, and the serial field was filled in with the correct value. How do I stop that from happening? > -----Original Message----- > From: Patrick Dunford [mailto:[EMAIL PROTECTED]] > Sent: Sunday, 11 February 2001 14:59 > To: PostgreSQL List > Subject: ODBC driver issue in MS Access > > > I installed the ODBC driver for Postgre, and linked in a table > which has a Serial field for the primary key. In MS Access, the > type is shown as just "Number (long integer)". > > When I try to add new records to my database in Access, I don't > put anything into the key field because the server is supposed to > generate it automatically. But when my record is sent back to the > server, it rejects it and Access displays "#Deleted" in all of > the fields. Is this because Postgre can't fill in the key field > and so rejects it as an integrity constraint violation? I don't > get any errors from Access. > > Should my database create its own key values and store them itself? > > ======================================================================= > Patrick Dunford, Christchurch, NZ - http://pdunford.godzone.net.nz/ > > In this way, love is made complete among us so that we will have > confidence on the day of judgment, because in this world we are > like him. > -- 1 John 4:17 > http://www.heartlight.org/cgi-shl/todaysverse.cgi?day=20010210 > ======================================================================= > Created by Mail2Sig - http://pdunford.godzone.net.nz/software/mail2sig/ >