Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 4DF342E003D for ; Sat, 14 Jun 2008 11:11:33 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 66623-04 for ; Sat, 14 Jun 2008 11:11:24 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by developer.postgresql.org (Postfix) with ESMTP id EFA022E0038 for ; Sat, 14 Jun 2008 11:11:29 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 16so3298473fgg.23 for ; Sat, 14 Jun 2008 07:11:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=osg/PnGuI+to5Sqxe/gMMJNJRZCV4q0lJu+0XqPebFI=; b=eGBXTtpD5HtCagwPG2nCB9o+v/Y7fW58VhVp2rjBVxdt8YOf71FY07FWgsdhqWwmHJ /a59/k+AopNOyIV3Xw2X0N4P25g9jSPuIgV6iOe2WKPKUwLyi03uep3Y5o8G27odI0PJ C7MZewKovJr5IiS1JD54h/QchNanTLyZbNRf4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=QmHxJWA7vyDNQXu+aolqDSYPAQlSmX3J6KIRWhO1yW05bO+DqVxwSNWnxkwH6V7uCd eqovCNATgZZdtVn+z/YQAFzElWvs58F05istXXTzy9fB0XcIxgExI40jUbn4ixXtdsQp Lev6mWAF9EuTeoR67V7Zc5hvWJw2Oh5TV9O8Y= Received: by 10.86.66.19 with SMTP id o19mr5716369fga.62.1213452687844; Sat, 14 Jun 2008 07:11:27 -0700 (PDT) Received: by 10.86.3.14 with HTTP; Sat, 14 Jun 2008 07:11:27 -0700 (PDT) Message-ID: Date: Sat, 14 Jun 2008 19:41:27 +0530 From: "C K" To: "pgsql-admin@postgresql.org" Subject: Storing images and other data in PostgreSQL from Ms Access MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_32932_13617142.1213452687856" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200806/116 X-Sequence-Number: 29454 ------=_Part_32932_13617142.1213452687856 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi All, I am testing the postgresql as a back-end for a project having ms access as a front-end. I have linked postgresql tables and started using. It works well for all data except the binary data. When used to insert/retrieve data from such fields, ms access gives error that it can't recognize the data. What to do? As per my knowledge postgresql adds some bytes to the binary data to be uploaded. I have eralier used mysql and it work well. Is there any solution for this? Please help. I am using Postgresql 8.3.1 and unicode driver with MS Access 2003 and most current patches from microsoft applied on Windows Xp. Thanks CPK -- Keep your Environment clean and green. ------=_Part_32932_13617142.1213452687856 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi All,
I am testing the postgresql as a back-end for a project having ms access as a front-end. I have linked postgresql tables and started using. It works well for all data except the binary data. When used to insert/retrieve data from such fields, ms access gives error that it can't recognize the data.
What to do? As per my knowledge postgresql adds some bytes to the binary data to be uploaded. I have eralier used mysql and it work well. Is there any solution for this?

Please help.
I am using Postgresql 8.3.1 and unicode driver with MS Access 2003 and most current patches from microsoft applied on Windows Xp.

Thanks
CPK

--
Keep your Environment clean and green. ------=_Part_32932_13617142.1213452687856--