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 8B43C9DD6A9 for ; Thu, 1 Dec 2005 14:40:55 -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 16114-08 for ; Thu, 1 Dec 2005 14:40:50 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from qsmtp2.mc.surewest.net (qsmtp.mc.surewest.net [66.60.130.145]) by postgresql.org (Postfix) with SMTP id C803A9DD43B for ; Thu, 1 Dec 2005 14:40:50 -0400 (AST) Received: (qmail 31821 invoked from network); 1 Dec 2005 10:39:39 -0800 Received: by simscan 1.1.0 ppid: 31805, pid: 31806, t: 1.4357s scanners: regex: 1.1.0 attach: 1.1.0 clamav: 0.84/m:34/d:1142 spam: 3.0.3 Received: from unknown (HELO chris) (65.78.162.90) by qsmtp2 with SMTP; 1 Dec 2005 10:39:38 -0800 From: "Chris Moore" To: "'Campbell, Greg'" Cc: Subject: Re: Data showing up as #Deleted in Access Date: Thu, 1 Dec 2005 10:40:48 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcX2nDOKMry6rqdnSKy/Hn2Z+YDqrgAChx/g In-Reply-To: <438F31C3.4020205@us.michelin.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20051201184050.C803A9DD43B@postgresql.org> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.927 required=5 tests=[MSGID_FROM_MTA_ID=0.927] X-Spam-Score: 0.927 X-Spam-Level: X-Archive-Number: 200512/4 X-Sequence-Number: 6483 I verified that the primary key was correct, and also turned on row versioning, but still got the same thing. Then I noticed that it was only one particular table that was having problems. It occurred to me that this table had several fields of type "text", one of which had rows in which this field had close to a thousand characters in it. I changed all the "text" fields to "varchar", making the one big one a varchar(2048). That seems to have fixed the problem. By the way, I did try searching for "#Deleted", but the search engine tries to be helpful and also find instances of "delete", "deleting", etc. There were just too many hits to be able to weed through them all and find the relevant ones. Thanks for your help. Chris