X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id AE03011F677A for ; Fri, 7 Apr 2006 17:00:42 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 24830-07 for ; Fri, 7 Apr 2006 17:00:38 -0300 (ADT) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 4BDC511F66CE for ; Fri, 7 Apr 2006 17:00:40 -0300 (ADT) Received: from mail.herbers.ca (unknown [64.56.146.223]) by svr4.postgresql.org (Postfix) with ESMTP id 86DE15AF85F for ; Fri, 7 Apr 2006 20:00:40 +0000 (GMT) Received: from localhost (unknown [127.0.0.1]) by mail.herbers.ca (herbers) with ESMTP id A36561EE17C; Fri, 7 Apr 2006 14:00:35 -0600 (MDT) Received: from mail.herbers.ca ([127.0.0.1]) by localhost (trusty.herbers.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29123-16; Fri, 7 Apr 2006 14:00:33 -0600 (MDT) Received: from [10.1.1.51] (unknown [10.1.1.51]) by mail.herbers.ca (herbers) with ESMTP id A49891EE17B; Fri, 7 Apr 2006 14:00:33 -0600 (MDT) Message-ID: <4436C4E0.9010205@herbers.ca> Date: Fri, 07 Apr 2006 14:00:32 -0600 From: James Herbers User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: C K Cc: "pgsql-admin@postgresql.org" Subject: Re: MS Access and PostgreSQL References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at herbers.ca 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: 200604/76 X-Sequence-Number: 21245 Microsoft has a KB article here - http://support.microsoft.com/kb/q128809/ - you may want to look at. I found the best way to avoid this was to use pass-through queries. J Herbers C K wrote: > Dear Friends, > I am here for a problem regarding MS Access and PostgreSQL connection > through ODBC. I have liked my PostgreSQL database tables to MS Access. > When I am going for inserting/updating any data is just displays > #deleted. I also use MySQL (client's choice). Same problem occurs for > MySQL also. But when I set the 'Return matching rows' option from > MyODBC 3.51.12 interface. the problem mostly gets solved. Other things > required are PK (or Unique column), a timestamp etc. I have done all > these for POstgreSQL, but it doen't work. Is there any option as > 'Return matching rows' for PGODBC? Or How I can solve this problem? > Please help. > Thanks and Regards. > CPK > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match >