>>Dunno Agnes, but if you were to create a cursor with a general field, append general and use that field in the cursor to display it on your form ?
>
>I don't like the idea of using general fields, though for one record cursor it may be a solution.

I've seen a solution like that used once upon a time ('99-01, IIRC) for a report, and it worked... until there was a workstation where some demo of graphic software which was tried and uninstalled, leaving absolutely nothing in charge of .jpg files. Of course, not our doing at all, but it ended with our app not working. If it only printed a blank square that'd have been fine, but it actually gave an ugly error message.

This way or other, for hosting other filetypes we have to rely on other software. I'm somehow more at ease with shellexecute() and other things which would give me a trappable error in case this other software is misconfigured, absent or just not cooperating. With general fields, the errors may be harder to catch - if for no other reason, then because so very few people use them, there was nearly nothing done about them since VFP5, and the knowledge about them is limited.