The type field « Image » on SQL-Server is a misnomer and should have been
called Binary or LongBinary or something like that instead of Image: it can
be used for storing any kind of binary data - including images. However,
Access - with either MDB or ADP files - has a peculiar way of storing images
in a database: instead of directly storing their binary content, it stores
their names only or it transforms them to OLE objects before storing them
into in OLE field (for MDB) or an Image field (for SQL-Server).
You should look into the Access newsgroup for answers about using and
storing images with Access; the solutions are the same for both MDB files
and ADP projects.

Signature
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
> Hello:
>
[quoted text clipped - 13 lines]
> Thanks
> Brennan
Sylvain Lafontaine - 07 Oct 2005 22:09 GMT
The last time I stored images in a ADP project, I used a Bound Object Frame,
opened the image in MS-Paint, copied it to the clipboard and then pasted
into the bound object. However, if I tried to copying and pasting the image
directly into the bound object frame without using the clipboard, this
didn't worked; ie. only the name of the image was visible and I had to
double-clicking it to see it.
The way Access stores and manipulates images with its standard controls is
simply nut and it's capabable of driving anyone crazy. An easier solution
would be to use a commercial control like DBPix.

Signature
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF
> The type field « Image » on SQL-Server is a misnomer and should have been
> called Binary or LongBinary or something like that instead of Image: it
[quoted text clipped - 27 lines]
>> Thanks
>> Brennan