>>>Does anyone know of any other tools or techniques that could be used to render .FRX reports into .JPG images accurately?
>>
>>How about output to a PostScript driver and then using GhostScript to convert .ps to .jpg? GS is amazingly fast - I was really surprised when I tried it. Though, I wasn't printing to a .ps, I was generating a .ps file (which is also fast when done in VFP), simply because I needed a special image generated on-the-fly.
>
>I've now tried this. The problem is exactly the same as with XFRX and FRX2Any. Each report page includes embedded .BMPs with .MSK files that aren't handled correctly.
>
>I thought that by going the .PS/GhostScript route it would solve the problem, it should simply be redirecting the output that would have gone to a printer, to a .PS file, then converted. But somehow, that is not the case. It's strange that the problem is the same. I'm wondering if it's something simple such as the .BMP and .MSK files have to be in the same folder as the .FRX when it's printed, or what. Especially strange since native VFP6 Preview or Print always works 100% correctly.

Then it could be that either your PS driver has the same problem, or that your assumption about directories is correct... or something in a totally different direction.

>Sidebar: the quality of the .JPGs generated by GhostScript via PostScript are not as good as the GDIPlus-generated output of XFRX/FRX2Any, and typical file sizes are 4x as large.

Yes, I've noticed that; haven't tried GDIPlus, but rather set GhostScript to generate PNG files instead. About the same quality with half the size, or twice the quality with about the same size. I needed the images for a webpage, so PNG was OK for me.