>I have a report that has an image on it, and I have noticed that it won't print on some PC's. I either get an empty space where the image should be or an OLE error.
>The only connection seems to be that the .BMP file extension on these PC's is being handled by something other than Microsoft Paintbrush.
>What program is the FoxPro report writer trying to access via OLE to print a graphic on a report? Is it the file extension association for .BMP files causing the error, or is there some registry setting that has been modified by graphics programs causing the problem?
>If anyone knows exactly how .BMP files are printed in the report writer via OLE I'd sure like to hear about how it works.

Hello, Lance.

This happens when you use general fields. General fields store a lot of information about the application that have to handle it, and indeed store a LOT of information mostly uneeded. Just append a 2K bytes BMP to a DBF and look how much it's FPT file size grows.

That said, it is better to store just a filename and store your images in some shared directory. Our approach is to let the user select the image file, then we copy it to the images directory renamed with a serial number, and we store this number as a key in our tables.

This is a little extra work, bu I highly recommend it as general fields bloats the memo files terribly, are quite unreliable, and have that kind of ole problems. Also, there is no straight way to extract the bmp from the general field. I wrote a function to do that, but it's just a kludge.

Hope this helps.