Received: from sid.trust.ee (sid.trust.ee [194.204.23.180]) by hub.org (8.8.8/8.7.5) with ESMTP id KAA19317 for ; Tue, 12 May 1998 10:52:11 -0400 (EDT) Received: from trust.ee (wink.trust.ee [194.204.23.184]) by sid.trust.ee (8.8.7/8.8.7) with ESMTP id RAA05456; Tue, 12 May 1998 17:51:40 +0300 Message-ID: <35586251.D6B32970@trust.ee> Date: Tue, 12 May 1998 17:53:05 +0300 From: Hannu Krosing X-Mailer: Mozilla 4.05 [en] (Win95; I) MIME-Version: 1.0 To: Ewan Mellor CC: PostgreSQL Interfaces Subject: Re: [INTERFACES] MS Access & PsqlODBC: Invalid field name 'name' References: <35582955.5F014F7B@nexus.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Ewan Mellor wrote: > > I am using Byron's ODBC driver (version .0239 downloaded today) with > Access 7.00 under Win95 with Postgres 6.3. I am trying to link tables > into Access. Most tables work fine, but any field with the name 'name' > or 'sortname' or even 'garbagename' may not be used as part of an > index. This occurs whether the index is picked up automatically by the > driver, or if you are asked to choose a unique field by Access. Starting from v2.0 of Access the worn "name" became kind of reserved word in Access, as the table itself aquired an _attribute_ name, which contains the name of the table. so having a field called name is a problem in anyway (for Access). I have no idea why "sortname" or "garbagename" does not work. > Can this be fixed? As a workaround, could the driver optionally not > tell the client application about indices? In this way, I could tell > Access to ignore them and then (I think) I would be able to get at my > data. you can still do ALTER TABLE yourtable RENAME name TO not_name_any_more; ------------- Hannu