There also might not be any OCX, the file type ESD only is associated with the easy street draw software and only it reads and displays ESD images.
Assuming you added an OLE control on your form and the "Insert Object" dialog picked "create from file", that's not giving you the superpower to see file contents in the way software associated with it can display it. The Olecontrol needs an OLE Server, that's an OLE class capable to handle that file. In the simplest case, the ole control will just display the file icon as a Windows Explorer window does when the view is set to icons. And in the worst case, VFP finds some partial type info of such an OLE server, but it isn't registered or not for common use.
Certain OLE servers/classes/controls only work in specific containers. For example, VFP comes with licenses for a few controls you can also redistribute royalty-free, but it's well known that even with such a license the usage is limited. For example, Winsock must be added to a form, you can't use a Winsock instance standalone. See
That's not a big restriction, it just shows there are such possibilities.
It's not the message you get, but the underlying reason could be the same, anyway.
If this is about an image, the usual solution is exporting as a type VFP supports: BMP, GIF, PNG, JPG.
Bye, Olaf.
Olaf Doschke Software Engineering