Re: Storing images and other data in PostgreSQL from Ms Access

["C K" <shreeseva.it@xxxxxxxxx>]

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@xxxxxxx> 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 écrit :

> 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=
=agg/
-----END PGP SIGNATURE-----

-- 
Keep your Environment clean and green.