For case 1, take a look at BINARY LOAD. You can create a QlikView associative model and use it to be loaded into other applications. If you need to share a visual item, for example a new sheet, you could create a new document and navigate to it from another documents using DOCUMENT CHAIN.
For case 2, maybe you should review your license model in order to jump to another than fits you better... Or think in create reports and share them (NPrinting).
I really liked the BINARY LOAD, it's a pity that i dont use tow or more Binary in sequence, just one in .qvw
The DOCUMENT CHAIN is very good too, but in qlik web dont works,at least not in ajax client...
Yeah, maybe i need buy more licences, perhaps this will be the better...
Thanks again Héctor.