Received: from mail.id-pro.net (qmailr@mail.id-pro.net [195.52.215.12]) by hub.org (8.8.8/8.7.5) with SMTP id QAA10966 for ; Wed, 3 Jun 1998 16:24:55 -0400 (EDT) Received: (qmail 31991 invoked from network); 3 Jun 1998 20:24:36 -0000 Received: from ts1-f3.kunden.id-pro.net (HELO automatix) (195.52.215.195) by medusa.id-pro.net with SMTP; 3 Jun 1998 20:24:36 -0000 Received: by localhost with Microsoft MAPI; Wed, 3 Jun 1998 22:29:21 +0200 Message-ID: <01BD8F3F.0DCE7DF0.tim@bosinius.de> From: Tim Bosinius To: "'David Hartwig'" Cc: "'pgsql-interfaces@postgreSQL.org'" Subject: RE: requested Logfile - Access97 Date: Wed, 3 Jun 1998 22:29:16 +0200 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 22 TEXT >You must have specified a multi-part key. If you cut this query out and run >it in the psql monitor you will see that it is a problem in the backend >server. We are currenly discussing how to resolve the problem. Hopefully it >will be resolved in the next release. I followed the issue on the mailing list. I believe that the backend should handle it. So - Method 3 in your mail to Hannu Krosing ;) > In the mean time. There is something >you can do for queries. Turn off "Recognize Unique Indexes", and relink the >tables in Access. When you relink do NOT select a primary key. This will >greatly speed your queries, but the table will be read only. Ok - this works pretty good. I created two ODBC entries for the same database/table one for my VB program the other for Access97(I need this for Winword documents) Byron said that version 244 will fix the MS Query problem. which is even better than using Access. (Maybe that also helps Jose' Soares Da Silva problem?! - see mailinglist) Regards, Tim Bosinius