>>We have ASelObj when modifying forms or classes. This allows us to know the currently selected object (or objects), from which we can learn the PEMs and their values, sibling objects, child objects, and the top-level object being edited, and other functions and methods allows us to create PEMs, and remove child objects, etc.. All of PEM Editor depends on this.
>>
>>I have never heard of any similar feature when using the Report Designer. Without it, I think this suggestion can go nowhere.
>
>I know that there is no aselobj() in RD. However when you select multiple report textboxes for instance, VFP/RD knows which are those.
>There is some clipboard info filled in somewhere (where ??) which is then used by VFP/RD to copy them. Content of that clipboard (where ever it is kept) is what I am after. Any ideas how this info can be retrieved ?

No ideas on how to solve this from this quarter. Without detailed knowledge of the structure of these objects in the clipboard, I would say this is pretty hopeless.

BTW, if you selected one or more controls in Form or Class Designer, you can access all of them without resorting to the clipboard (ASelObj again). I have no idea how you could import them into an open instance of the Report Designer. I can imagine, however, that it would be possible to import them programmatically into the FRX.

The other direction, FRX to VCX/SCX is more of a problem, because then you would have to access and interpret the contents of the clipboard.