Thanks for the info Larry; I did find a free utility that allowed me to download the objects as JPGs to a directory. The objects turned out to be indeed Word documents that were uploaded to the database. I found out that when you load photos or documents to Access and store them internally, they increase in size from 10-20 times...no wonder that the 90+ documents stored ballooned the database to over 200 Mb; thank God for R:Base. The Word documents contain photos and information on the equipment in question; I don't understand why anyone would want to store this information on an uploaded Word document instead of storing the data in columns in the equipment table. I will find out if the client still has the original photos and load a link to them in the R:Base database as I prefer to store them on a sub-directory.
Javier, Javier Valencia 913-915-3137 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lustig Sent: Friday, May 02, 2008 10:09 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Question on importing data from Access << PhotoLocationID OLE Object >> These pictures are wrapped in a bunch of stuff to make them function as documents that can be fed into another application for processing. I would expect them to be associated with a graphics application, but since they say MS Word it may, in fact, be that people "created" the images in Word. In any event, I don't think there's any way to read them directly from R:Base. You'll need to either write an Access program to save the contents of each file to an image file that R:Base can read, then an R:Base program to consume the files, or else a program that will loop through the Access records, extract the image part of the file in memory, and then use an ODBC connection to the R:Base database to push the image into a varbit column. I would imagine the first option would be much easier to code since you could examine the intermediate files with Paint or something to ensure they are valid JPGs. The second method requires you to manage memory fairly directly. -- Larry
