X-Original-To: pgsql-odbc-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 603B99DD70B for ; Fri, 2 Dec 2005 06:36:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34121-07 for ; Fri, 2 Dec 2005 06:35:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr2.postgresql.org (svr2.postgresql.org [65.19.161.25]) by postgresql.org (Postfix) with ESMTP id 98D609DD6D7 for ; Fri, 2 Dec 2005 06:35:58 -0400 (AST) Received: from mail.cibal.es (97.Red-80-59-70.staticIP.rima-tde.net [80.59.70.97]) by svr2.postgresql.org (Postfix) with ESMTP id 7A5AAF0BBE for ; Fri, 2 Dec 2005 10:36:00 +0000 (GMT) Received: from Miguel ([192.168.200.7]) by cibal.es (mail.cibal.es [192.168.200.2]) (MDaemon.PRO.v8.0.1.R) with ESMTP id md50000056686.msg for ; Fri, 02 Dec 2005 11:35:23 +0100 Message-ID: <00ed01c5f72c$1c1a3b30$07c8a8c0@Miguel> From: "Miguel Juan" To: References: <438F31C3.4020205@us.michelin.com> <20051201184050.C803A9DD43B@postgresql.org> <20051201195932.GA16735@soptik.pzkagis.cz> Subject: Re: Data showing up as #Deleted in Access Date: Fri, 2 Dec 2005 11:35:26 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2527 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 X-Spam-Processed: mail.cibal.es, Fri, 02 Dec 2005 11:35:23 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 192.168.200.7 X-Return-Path: mjuan@cibal.es X-MDaemon-Deliver-To: pgsql-odbc@postgresql.org X-MDAV-Processed: mail.cibal.es, Fri, 02 Dec 2005 11:35:23 +0100 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[none] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200512/71 X-Sequence-Number: 6550 Hello, There is a workaround, just check the "Show OID column" and "Fake index" in the ODBC configuration. This used to work for me (some time ago, I must say). Regards, Miguel Juan