Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 49A0D2E0073 for ; Sun, 15 Jun 2008 10:41:30 -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 18354-08 for ; Sun, 15 Jun 2008 10:41:21 -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.154]) by developer.postgresql.org (Postfix) with ESMTP id 9E3872E0035 for ; Sun, 15 Jun 2008 10:41:26 -0300 (ADT) Received: by fg-out-1718.google.com with SMTP id 16so3415848fgg.23 for ; Sun, 15 Jun 2008 06:41:24 -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:cc:in-reply-to:mime-version:content-type:references; bh=0xJGu2aIL8GL2Ce50Jm/ll+eH4Fdv6FYhiQiptdv3RI=; b=TNtC3HvgEWUTBq43GIhdb8ERHpCKOvdlRL10GpsJsLlPwQIAn9sz+nrmFuRkeQVsVJ rITT2ZDLwX145QTNz+pPAjHlPY9v9kkn1qBu0rTWFq8tu1zuUNhL/CdeysLZO02dClPz jgGjhrRYy8CJszVrv9G12mR5a+0U4S4/ZVvQY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=s0TnIxLg8oCbHZBVwk/jb9Pe9xP+c3BdZxSoEMj83dYuG+MPC4Qz6wBjIM8mnZmoXX w0EJtCSyW2i4UOBXFSntl00dlBCZE0CGnq4HIglCNJeJIAlzKf/cI8I50y8vcdFU+oSS HZOK4F37J/tJ3v+giVIz9dLRn3lmXnd0cFjVU= Received: by 10.86.99.9 with SMTP id w9mr6929748fgb.70.1213537284798; Sun, 15 Jun 2008 06:41:24 -0700 (PDT) Received: by 10.86.3.14 with HTTP; Sun, 15 Jun 2008 06:41:24 -0700 (PDT) Message-ID: Date: Sun, 15 Jun 2008 19:11:24 +0530 From: "C K" To: "JGuillaume (ioguix) de Rorthais" Subject: Re: Storing images and other data in PostgreSQL from Ms Access Cc: "pgsql-admin@postgresql.org" In-Reply-To: <48548ECB.1070700@free.fr> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_996_9491119.1213537284769" References: <48548ECB.1070700@free.fr> 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/118 X-Sequence-Number: 29456 ------=_Part_996_9491119.1213537284769 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline No need to do it. On the web I found a article which states to use the data type 'lo' rather than 'bytea' and after refreshing the link works well. No problem faced. tested with MS access 2003 and 2007. Thanks to community. CPK On Sun, Jun 15, 2008 at 9:08 AM, JGuillaume (ioguix) de Rorthais < ioguix@free.fr> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > *IIRC*, using bytea type works like a charm for OLE stuff from MS > Access... > > Try to link your tables with the ANSI driver, then change the ODBC > source to the UNICODE one. I don't know why, but ISTM that MSAccess > perform a better type mapping with the ANSI driver...at least, TEXT -> > Memo, so I probably linked bytea -> OLE using the ANSI driver when I > tried ? > > - -- > Guillaume (ioguix) de Rorthais > > C K a =E9crit : > > 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. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFIVI7KxWGfaAgowiIRAhwLAJoCIPP6kWoZGsvdNJvkKx38xIUtaQCeKYrk > ah6gAsw1uMVhqFENBhgR9jk=3D > =3Dagg/ > -----END PGP SIGNATURE----- > > --=20 Keep your Environment clean and green. ------=_Part_996_9491119.1213537284769 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline No need to do it. On the web I found a article which states to use the data= type 'lo' rather than 'bytea' and after refreshing the lin= k works well. No problem faced. tested with MS access 2003 and 2007. Thanks= to community.
CPK

On Sun, Jun 15, 2008 at 9:08 AM, JGui= llaume (ioguix) de Rorthais <ioguix@fr= ee.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

*IIRC*, using bytea type works like a charm for OLE stuff from MS
Access...

Try to link your tables with the ANSI driver, then change the ODBC
source to the UNICODE one. I don't know why, but ISTM that MSAccess
perform a better type mapping with the ANSI driver...at least, TEXT -> Memo, so I probably linked bytea -> OLE using the ANSI driver when I
tried ?

- --
Guillaume (ioguix) de Rorthais

C K a =E9crit :
> 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.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIVI7KxWGfaAgowiIRAhwLAJoCIPP6kWoZGsvdNJvkKx38xIUtaQCeKYrk
ah6gAsw1uMVhqFENBhgR9jk=3D
=3Dagg/
-----END PGP SIGNATURE-----




--
Keep your Environment c= lean and green. ------=_Part_996_9491119.1213537284769--