The application on your system that is registered to display the selected
Image type is not able to fully function as an OLE Image server in Access.
In this case it inserts the Image as a Package object.
What is the image type you want to insert as an OLE object?
Do you understand that embedded OLE images are stored as uncompressed
Bitmaps? Further, the uncompressed Image is actually stored twice for all
intensive purposes? This means you will not be able to store many images and
your MDB will quickly bloat in size? Do you really need to store the Image
an OLE object?
The accepted method is to NOT use the Bound or Unbound OLE Frame controls.
Instead use the standard Image control. In the Current event of a form or
the Detail section of a report, load the image into the Picture property of
the Image control with code like:
Me.NameOfTheImageControl.Picture = "C:\Wherever\TheNameOfYourImage"
See:
http://www.mvps.org/access/forms/frm0030.htm
(Q) Instead of storing the images in a table, I'm now string the path and
filename of the files in a table, and using the Image control. However, I
don't want the "Loading Image" dialog to come up. How can I hide this
dialog?
(A) The "Loading Image" dialog is popped up by the filter that's processing
the image. We don't have any direct control over it.
There are two ways to prevent the dialog from coming up.
1.. By changing a registry setting emailed to me by Klaus Oberdalhoff.
HKEY_LOCAL_MACHINE\Software\Microsoft\ Shared Tools\Graphics
Filters\Import\JPEG\Options
Change the ShowProgressDialog key value to "No".
If you go with standard Image control then you need to modify an entry or
entries in your Registry to disable the "Loading Image" dialog.
See:
http://www.mvps.org/access/api/api0038.htm
Here is a previous post of mine on this issue.
The one thing you must do is turn of the Loading Image dialog. If you don't,
and quickly scroll through the records in Form view, or page quickly in
Print Preview, you run the risk of crashing Access. Use the Registry mod at
the Access MVP site:
Additionally, two issues in regards to the Registry modification pointed to
here
http://www.mvps.org/access/api/api0038.htm
1) The Registry key MUST be "No" NOT "no" or "NO"
2) On systems with XP or on systems with more than one user account,
you must add/modify the key in both HKEY_CURRENT_USER and
HKEY_LOCAL_MACHINE.
--
HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.