Hi Steve, I would add two other items.
1) Turn of the "Importing Image" dialog window via the registry keys as
outlined here:
 http://www.mvps.org/access/api/api0038.htm
Make sure you do it for all Image types that you using that contain the
key.


2) Change all of the Images to Bitmaps at runtime. I have been able to
print previously unprintable reports by doing this last step. Here's a
previous post of mine on the subject.


From: Stephen Lebans (StephenLebans@mvps.org)
Subject: Re: Images in Reports
View: Complete Thread (18 articles)
Original Format
Newsgroups: microsoft.public.access.reports
Date: 2002-09-16 18:46:39 PST


Bruce I finally got a chance to test your method last night. It helped
but only with the actual printing and not the Print Preview itself.
 I was able to print the failed Report directly to the printer or to a
disk printer file so that's great! Don't get me wrong, it's still a good
thing because at least you can print the report!

Unfortunately Acess still runs out of resources when you page back and
forth through Print Preview.
I plan to spend some time onthis issue shortly.
Here is the code I use to convert any Jpeg, Gif, or Metafile into a BMP.
Rather than using one of my API solutions I have cheated and set a
Reference to Standard OLE Types type library in order to get at the
SAVETODISK method. But no ActiveX controls are required


Private Sub Detail_Print(Cancel As Integer, PrintCount As Integer)

Private ctr As Long

ctr = ctr + 1

Select Case ctr
    Case 1
     Me.Image10.Picture = CreateBitmapFile("C:\A.jpg")

    Case 2
    Me.Image10.Picture = CreateBitmapFile("C:\b.jpg")

    Case 3
    Me.Image10.Picture = CreateBitmapFile("C:\c.jpg")
    ctr = 0

    Case Else
    ctr = 0

End Select

End Sub

Private Sub Report_Open(Cancel As Integer)
ctr = 0
End Sub


Private Function CreateBitmapFile(fname As String) As String

Dim obj As Object

Set obj = LoadPicture(fname)
If Not IsNull(obj) Then

SavePicture obj, "C:\SL11-52"
DoEvents
End If


CreateBitmapFile = "C:\SL11-52"
Set obj = Nothing

End Function

This post is basically just to document the solution I achieved for
the lack of Microsoft Photo Editor in Office 2003. I will admit it's
worthless if you don't have a previous version of Office available.

All my documentation projects involve a _lot_ of screen captures. Now,
I suppose I'm lazy for not setting up proper graphics folders and
indexes and all that for all the screen captures, but I find the
documents themselves provide all the organization of the images that I
need.

The major drawback to this occurs when an image needs to be edited.
Once an image is in a Word document, Word will not hand it off to
another application (via copy/cut and paste) in its original form.
Lettering becomes blurred and distorted. And even the seemingly
logical solution of saving the file in HTML format, where images are
saved as separate files, does not produce usable results.

The only application that Word will hand the image to without
distortion is Microsoft Photo Editor. But Microsoft Photo Editor is
not part of Office 2003.

Ever since this image handling peculiarity showed up with Word 97, the
method I've used is: copy the image from the Word document, paste it
into Microsoft Photo Editor, then copy it from there and paste it into
Paint Shop Pro. Edit it, and from Paint Shop Pro copy and paste it
back into Word. (My edits generally involve things that can't be done
in Photo Editor.)

So, the answer is to install Photo Editor from a previous version of
Office. In my case, my previous version was Office XP.

Using the Custom installation option in Setup for the old version of
Office, make sure that _everything_ is marked "Not Available", except
for Photo Editor. Run the installation.

This will, however, install some other shared files that will cause
problems with Office 2003. For example, after installing Photo Editor,
Outlook 2003 threw many errors. 

So, the next step is to use the Office 2003 installation CD to run the
Repair Office Installation function.

Everything seems to be running fine now. I can get undistorted images
out of Word via a stopover in Photo Editor, and Word and Outlook are
running without errors.

I don't understand why it's not possible to copy and paste an image
from Word to my graphics software without distortion, I just know it
is. And, for now, there's still a workaround, although Microsoft's
discontinuance of Photo Editor does not bode well for the future.

-- 
Email address munged. You can figure it out.

I did this in a vain attempt to regain some thumbnails. What I've found is
that now Office Update keeps prompting me to update Office XP. <sigh>

--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://www.word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.

"CAndersen (Kimba)" <KimbaWLion_aol.com@127.0.0.1> wrote in message
news:44070b6aad018c4386e8cfcfa648c0e4@news.teranews.com...
> This post is basically just to document the solution I achieved for
> the lack of Microsoft Photo Editor in Office 2003. I will admit it's
> worthless if you don't have a previous version of Office available.
>
> All my documentation projects involve a _lot_ of screen captures. Now,
> I suppose I'm lazy for not setting up proper graphics folders and
> indexes and all that for all the screen captures, but I find the
> documents themselves provide all the organization of the images that I
> need.
>
> The major drawback to this occurs when an image needs to be edited.
> Once an image is in a Word document, Word will not hand it off to
> another application (via copy/cut and paste) in its original form.
> Lettering becomes blurred and distorted. And even the seemingly
> logical solution of saving the file in HTML format, where images are
> saved as separate files, does not produce usable results.
>
> The only application that Word will hand the image to without
> distortion is Microsoft Photo Editor. But Microsoft Photo Editor is
> not part of Office 2003.
>
> Ever since this image handling peculiarity showed up with Word 97, the
> method I've used is: copy the image from the Word document, paste it
> into Microsoft Photo Editor, then copy it from there and paste it into
> Paint Shop Pro. Edit it, and from Paint Shop Pro copy and paste it
> back into Word. (My edits generally involve things that can't be done
> in Photo Editor.)
>
> So, the answer is to install Photo Editor from a previous version of
> Office. In my case, my previous version was Office XP.
>
> Using the Custom installation option in Setup for the old version of
> Office, make sure that _everything_ is marked "Not Available", except
> for Photo Editor. Run the installation.
>
> This will, however, install some other shared files that will cause
> problems with Office 2003. For example, after installing Photo Editor,
> Outlook 2003 threw many errors.
>
> So, the next step is to use the Office 2003 installation CD to run the
> Repair Office Installation function.
>
> Everything seems to be running fine now. I can get undistorted images
> out of Word via a stopover in Photo Editor, and Word and Outlook are
> running without errors.
>
> I don't understand why it's not possible to copy and paste an image
> from Word to my graphics software without distortion, I just know it
> is. And, for now, there's still a workaround, although Microsoft's
> discontinuance of Photo Editor does not bode well for the future.
>
> --
> Email address munged. You can figure it out.

On Wed, 17 Mar 2004 18:16:32 -0600, "Suzanne S. Barnhill"
<sbarnhill@mvps.org> wrote:

>I did this in a vain attempt to regain some thumbnails. What I've found is
>that now Office Update keeps prompting me to update Office XP. <sigh>

I'm sorry to hear that. I have not run into that problem.

However, Outlook did start throwing errors again after I posted. 
I found this (incredible) fix:
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off&threadm=081601c309fd%242ac4c3e0%24a001280a%40phx.gbl&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26safe%3Doff%26q%3Derror%2B8007007F%2B-%2Bthe%2BFIX!%26btnG%3DGoogle%2BSearch
(in case that breaks when I post it, here's a shorter link:
http://makeashorterlink.com/?M27B623C7
but I don't know when that short version will expire.)

I don't know if that fix will relate to your problem or not.
Component checker found that I had two different versions of
oledb32.dll on my computer, and that was confusing things.
So far, after doing the prescribed manual replacement of oledb32.dll,
Outlook is happy and I can still extract images from Word.