I'm so fed up. JPEG pictures worked find in 2000

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Helen Walters - 28 Sep 2004 18:38 GMT

I've browsed through the entire 117 titles on the forms
newsgroup and there were half a dozen or so questions
like mine, though the replies were mostly too technical
for me (thanks all the same)

In Access 2000 I could LINK jpeg files to OLE fields and
display a "thumbnail" image on each form. I understand
about linking rather than embedding; the Help files
showed how to do it, and it all worked fine.

I am an end-user trainer and have Access 2003, trying to
help acouple of users with Access XP - and although the
Help files explain how to do it in exacly the same way, I
can only display an icon or the filename.

I can't explain the current Event expressions (it'll take
me hours to grasp it myself) to these two novice Windows
users. Why won't it work any more? I'm depressed to
think that we have to stick with 2000 for this to work.
(The database when is likely to have around 2000 records -
thats not large is it?)

Can anyone from Microsoft tell me if this was a
deliberate change, or is there something wrong with my
settings somewhere.

I'll book myself on a course for Access Basic, or VBA but
hope I don't have to.....

Reply to this Message

Larry Linson - 30 Sep 2004 00:31 GMT

> In Access 2000 I could LINK jpeg files to OLE fields and
> display a "thumbnail" image on each form. I understand
> about linking rather than embedding; the Help files
> showed how to do it, and it all worked fine.

> I am an end-user trainer and have Access 2003, trying to
> help acouple of users with Access XP - and although the
> Help files explain how to do it in exacly the same way, I
> can only display an icon or the filename.

> I can't explain the current Event expressions (it'll take
> me hours to grasp it myself) to these two novice Windows
> users. Why won't it work any more? I'm depressed to
> think that we have to stick with 2000 for this to work.

> (The database when is likely to have around 2000 records -
> thats not large is it?)

No, that is not a large database, but it may be _huge_ if you store images
as OLE Objects.

When you store images in OLE Fields, you put yourself at the mercy of
whatever software the user has registered to handle the particular image
file type. You could have encountered a situation in which the newer
machines have a different COM-automation-enabled image processing program
registered for your image types.

The sample imaging databases at http://accdevel.tripod.com illustrate three
approaches to handling images in Access, and the download includes an
article discussing considerations in choosing an approach. Two of the
approaches do not use OLE Objects and, thus, avoid the database bloat, and
some other problems, associated with images in OLE Objects.

If you are printing the images in reports, to avoid memory leakage, you
should also see MVP Stephen Lebans' http://www.lebans.com/printfailures.htm.
PrintFailure.zip is an Access97 MDB containing a report that fails during
the Access formatting process prior to being spooled to the Printer Driver.
This MDB also contains code showing how to convert the contents of the Image
control to a Bitmap file prior to printing. This helps alleviate the "Out of
Memory" error that can popup when printing image intensive reports.

While at Stephen's site, take a look at his examples, classes, and (free)
controls for displaying images.

Larry Linson
Microsoft Access MVP

Reply to this Message