Cascading Embedded Elements?

Is it possible to have an embedded editor on an embedded editor on a form?

Specifically:

I want to have a Grandparent form that shows a list of Parent documents, using an embedded view that is targeted to an embedded editor (for the selected Parent document).

On the Parent form, used for the embedded editor (above) I want to show a list of Child documents using an embedded view.

So far, so good.

Here’s the problem: I want to target the embedded view on the Parent doc form (showing the Child documents) to target an embedded editor showing the Child document detail.

Grandparent document

  • embedded view of Parent docs

  • embedded editor showing selected Parent doc

    • embedded view of Child docs
    • embedded editor showing selected Child docs

As a Grandparent document is opened, the form will show a list of Parents, with the detail on the first Parent, as well as a list of Children (of the first Parent) and the detail on the first Child (in that list).

Anyone know if any of this is possible?

My first task is just to get this relationship to show - all the way down to the detail. I’ll worry about what can and can’t be edited after that.

Subject: Cascading Embedded Elements?

I was screwing around with this after reading your note and the second embedded editor simply refused to work for me, but the rest was fine.

HTH,

Dave

Chub Toad, LLC

Subject: RE: Cascading Embedded Elements?

Glad you were able to understand my rantings. I was a bit concerned about making my problem clear.

I appreciate the effort.

Subject: Cascading Embedded Elements?

I am thinking it is related to the way I am referring to the embedded editor (for the Child documents) from the Target Frame property in the view on the Parent form.

Does there need to be a “path” (or similar component) to the Target Frame property? The Parent form (with embedded Child editor) works fine when opened with the Parent document as the main form (as opposed to the Grandparent document as the main form). Does opening the Parent document from within the Grandparent form cause the Parent form to fail when trying to locate the embedded editor (for the Child form) since it is not “at the root”?