Received: from bush.rutgersinsurance.com (rutgersinsurance.com [38.138.71.194]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f03DxK782910 for ; Wed, 3 Jan 2001 08:59:20 -0500 (EST) (envelope-from aalang@rutgersinsurance.com) Received: from 6014cwpza006 ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id JAA30809 for ; Wed, 3 Jan 2001 09:04:02 -0500 Message-ID: <006e01c0758d$af569720$330a0a0a@6014cwpza006> From: "Adam Lang" To: References: <01C074E5.086196C0.mdavis@sevainc.com> Subject: Re: RE: ODBC-Problem Date: Wed, 3 Jan 2001 09:01:35 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200101/29 X-Sequence-Number: 638 Also, make sure the ODBC driver for postgres is set for updating. By default it is read only. Adam Lang Systems Engineer Rutgers Casualty Insurance Company http://www.rutgersinsurance.com ----- Original Message ----- From: "Michael Davis" To: Sent: Tuesday, January 02, 2001 7:54 PM Subject: [INTERFACES] RE: ODBC-Problem > Add a primary key index to the tables that you want to be able to update. > Access relies on the primary key for a lot of things. I recommend you add > a primary key to all postgres tables. > > -----Original Message----- > From: Evil Azrael [SMTP:EvilAzrael@EvilAzrael.de] > Sent: Sunday, December 31, 2000 8:50 PM > To: pgsql-interfaces@postgresql.org > Subject: ODBC-Problem > > HI > > I have just moved my old MS Access Database to a postgres database via > odbc. all went okay, and i can access the database in MS Access via > ODBC. Only a Client programm that i wrote can?t access the database > anymore via ODBC. The Visual BAsic Database programm says that the > database itself is updateable, but the tables in it aren?t updateable, > and all tries to connect to a table in VB via the OpenRecordset method > fail with the error message "parse error near [name of the table]" or VB > tells that it?s a connection error. > That?s weird. > MS Access has no problems connecting and writing to the database. > VB?s Visual Database Manager can connect to the database, but can only > read tables. > MY VB programm can?t even connect to the tables, but it worked quite > good via ODBC to the Access Database. > > > I don?t know what i can anymore, so please help if you know a solution. > > > Christoph Nelles