>Ed,
>
>thanks for the help.
>
>I did NOT use the LINK or CLASS keywords. I guess I was under the mistaken impression that VFP dealt with this itself. Questions:
>
>1 - How do I know what server is handling bmps ?
>

Look in HKEY_CLASSES_ROOT to find the association for .bmp

>2 - how do I set up a "server currently associated with the image file's extension" to work? Currently on these machines - bmps open in MS Paint. Will Ms Paint not suffice to render the image on the form?
>

It should work fine, but it should be the same product to service the image on all systems.

>3 - If I don't have a sever handling the OLE - how is the logo printing OK on the same machines that it WON'T display OK in the form?
>

This strongly implies a video driver issue.

>4 - Finally - is this the result of the fact that my dev machine does NOT have Ms Paint on it and uses paint shop pro to open bmps and these deve machines do not have paint shop pro? If so, why does it open Ok on an NT Server that has next to nothing on it?
>

No, as long as all the client machines are using MSPaint, there's no internal formatting issue. I'd look at the video mode of the server it works from.

>>Ken,
>>Two questions.
>>
>>When you filled the general field did you specify the class that will render the image and did you use the LINK keyword?
>>
>>If you did not use the CLASS keyword then the server responsible for rendering the image will be the server currently associated with the image file's extension.
>>
>>The LINK keyword instructs the OLE bound image to be linked to it's server where omission of the LINK keyword will embed a portion of the server's code with the image in the general field.
>>
>>One note of particular interest:
>>Microsoft will be issuing a Q article shortly about a documented bug with printing of OLE bound images. The VFP report writer ignores any attempt to associate your general field image with a particular class (via the CLASS keyword). The general field may be created correctly with the APPEND GENERAL and properly associated with the desired class but the report engine ignores this class designation and prints the image using the default association for the file's extension. Be warned.
>>
>>ED