The challenge with documenting the contents of a diagram is ‘how to decide the order of printing’? When eaDocX asks EA for the contents of a diagram, we get back a flat list of elements. eaDocX will group similar-formatting elements together, and print them in order of Element type, but we can’t go much beyond that: we just don’t know any more. Printing from diagrams works well when the diagrams are either in a section by themselves or when they live in a package with no other element: stops too many duplicates from printing.

You have some alternatives:
1 – Document Package B, which will print elements 3,4,5,6 , then specifically exclude element4
– not sure how you can tell eaDocX to print only those elements which relate to these, which are just the ones which are in a specific package: you can restrict by the type of element, and the type of connection, which is the more normal way to do things. Even if eaDocX could do this, it would be a very fragile way to model.
2- create an EA Model View, and put your elements into that, and print the Model View in its own section.

I didn’t include scripting as another alternative, but if you’re feeling brave, then this is also an option.
If the elements are of a predictable type/stereotype, then you can write a little script in EA which is in effect a tiny generator. So long as it creates a string of well-formed HTML, then eaDocX will use it.
Such a script can then to really clever things like checking the parent element of something which you’re printing, and only printing the ones you want.
There are some examples on the website.

It should be able to generate a document that small in a few seconds – something’s clearly gone wonky.
A couple of ideas:
1 – is your SQL query a well-behaved one? Does it have the structure which eaDocX expects (see help)
2 – do you have a glossary? We’ve just had a really strange ‘hanging’ error where Word became un-responsive as eaDocX was trying to create the glossary: it didn’t like looking for the glossary entry ‘EA’ ! Very odd one, this. If you have one, try removing it, and trying again.

The problem with losing the EA sort order is known. I thought we had a forum posting about it, but I can’t find it….
The problem is that as you create elements under a package, EA shows the elements in the order you created them. But they have no explicit sort order in the DB. Only when you move one up/down (with the green arrows in the Project browser) does EA write sorting data to the DB, which eaDocX can use.
So, if the order in eaDocX is different from that in EA, just pick an element, move it up, then back down, then eaDocX will get the explicit ordering information. Same is true for Packages under packages.