How to get OLE option "Image Document" in image box?

You must be referring to the attachment datatype in Access 2007.  The Attachment field datatype is used to store images, spreadsheet files, documents, charts and other types of supported files to the records in your database. This is a new feature that has been introduced with Microsoft Access 2007.

Attachments in Access 2007 replace the OLEDB data type of the older versions. However the OLEDB data type is continued for backward compatibility. Access 2007, of course, only allows the creation of the new data type.

See this for a tutorial on working with this new datatype:
http://www.cimaware.com/resources/article_135.html

Thank you for your response.

Well, the client in question has Office 2000 - not 2007 - on her computer.
Perhaps a little background information on what I am trying to do will help:
I have an access database table linked to a Sql Server table with a column of type Image.
It shows up as an OLE field when i open it up in access.
So, I found Stephen Leban's OLE To Disk utility (http://www.lebans.com/oletodisk.htm)
which exports all records of an OLE field to their respective original file formats. In this case, bmp and jpeg images.
The tool was only able to export half the images, claiming to not support records marked with the OLE type "Imaging.Document".
At first I thought this was an Office 2003 document imaging file, but it turns out the client who put this image in the database has office 2000 on her machine and was putting the image there by double clicking on an OLE container, selecting "Image Document" which automatically opens up a third party scanner/camera application called ArcSoft PhotoImpression 5, from which she captures an image from a camera, and drags/drops it in to the access form OLE container.

So, something other than office 2007 is enabling this "Image Document" OLE object - I tried installing the lastest version of ArcSoft photoimpression, which didn't do the trick.
Any other suggestions?

I believe that it is the 3rd party ActiveX (ArcSoft photoimpression) that is enabling the image document for your client.  You probably have a missing reference, and need to set a vb library Reference to the ActiveX.  If need be, have your client let you know what vb library references she has set on her machine.

Eh..
not sure what a vb library reference is, i'll guess it's a COM assembly reference used from access applications, correct me if i'm wrong.
Do i need to update this vb library reference on the export tool i'm using? if not there, where?
And how can I figure out what library reference I am missing?

Again apologies for the ignorance - I am not familiar with COM and classic vb that much.

Ok, I found no option in the assembly list for ArcSoft.
I don't see why that would make sense, why the developer of the application would add a reference to a dll that wouldn't exist for a few years (this is an old application, and ArcSoft photoimpression is my client's relatively new way of importing images to the application)

at this point I think I will just try and run the export procedure on that client's machine rather than on the database server - This needs to be resolved very quickly and I don't have time to sit and learn access development.

Thanks anyway

ok, but I would still get your client to give you a list of the vb library references that have been set on their machine.  It might be enlightening.

For the specific application, or is there some global cache of vb references?
I'm inclined to think it's not application specific, as it came up on the standard OLE object selection menu.

application specific-could it be a reference that was set by Leban's code that you mentioned previously?

I don't believe there is any reference set <<by a programmer>> to ArcSoft photoimpression.
Lebans code definately does not have it - it's a generic OLE extraction utility.
And the application which uses the image does not depend on the software to run, it simply launches it as a 3rd party imaging program. If the access application is installed on a machine without ArcSoft installed, it will not cause any problems.

I am not talking about the arcsoft application....I am talking about the Leban's application, itself. If you look at this link to Lebans like I just did, you will see that Leban's is using a special freely distributable DLL from Microsoft.  That may be your answer....download the DLL.

                      http://www.lebans.com/loadjpeggif.htm 

I see.
I will look into it.
Thanks for your help