Export table from QV to Excel

[Black_Hole]

Hello all,

I would like to export two straight tables from QVW to a unique Excel file where the first sheet (respectively the second sheet)  corresponds to the first table (respectively the second table).

I would like to know if it's possible to export without macro?

If is not, please could you help me to use the macro from this topic  but without using the "Document Properties set " because this part complicated if I want to share my QVW others users. 

Thank you in advance for you support.

[lironbaram]

hi 

you can build a report in nprinting , that export as many tables you want to the same excel file 

than using on-demand capabilities you can allow the user to export the report as part of the analysis process  

[Black_Hole]

Hello @lironbaram ,

Thank you for your reply.

I would like to keep using QVW because in my team, we have already the licence. 

And maybe, I don't understand the concept,  but from what I understood printing is another QV tool.

Please could you advise me about a stable solution to export in the environment of QVW.

Thank you in advance for your help.

[jerrysvensson]

First, you have to use plugin as client for a macro to work. That means, only using Internet explorer.

Using a macro is not a stable solution. NPrinting provides you with a stable solution.

It is another tool, but uses the data and diagrams built in your QlikView application.

[Brett_Bleess]

I cannot think of a means to export two different QlikView objects into the same Excel file without the use of a macro, the actions etc. I do not believe are going to behave any differently here as well.  About the only option I think would be to export to the two files and then use an Excel template with a macro there to join things as you want them I think, about the best option of which I can think here. 

Regards,
Brett

[Black_Hole]

Hello @Brett_Bleess , @jerrysvensson ,

Thank you both for your reply.

Today, the solution directly available is to use a macro so I will try in this way.

I hope that it will work effectively when my Qlikview will be deployed for many users.

[Brett_Bleess · Accepted solution]

The main issue in using macros is they cause the calculation engine to single-thread, which can cause timing problems in calculations in the entire app etc.  As long as you keep this in mind, and can work around those timing related issues, it should work.  The other issue is the Edit Module in QlikView is based upon VB version 3 I believe, really early release, so that can be an issue as well, and there is no plan to update that as far as I am aware, as we prefer folks use the Actions now, but some things are just not possible via Actions.  There is an Export action though, so if you have not looked at that, you may want to do so, just to be sure there is not something there that might work better than the macro.

Here is the Help for Actions, it is under the Button object, which makes the details a bit difficult to find:

https://help.qlik.com/en-US/qlikview/November2018/Subsystems/Client/Content/QV_QlikView/Button2.htm

Regards,
Brett

[Black_Hole]

Hello @Brett_Bleess ,

Thank you very much for this detailed explanation and for sharing the link.

It's good to know. 👍

Kind regards,