Can QV's data be exported to excel in "read only mode" ?

[#1]

Hi,

Is it possible to restrict the "export to excel " data in read only mode ?

End user should not be able to edit the data in excel after exporting it from QV

Thanks & Regards,

[#2]

Not that I am aware of using the Export in-built facility of Qlikview.

I believe we can try creating a macro(though not recommended) and then add functionality in their.

Thanks,

Singh

[#3]

Hi Angad,

Ya , we can try that but it's like inviting a trouble.

So don't want to do that.

Regards,

Sarang M. Mehta

Regards,

Sarang M. Mehta

Sent from Samsung Mobile

Please excuse the brevity of the message

[marcus_sommer]

You could use a master-file with appropriate security and copy+paste instead of export the data.

- Marcus

[sebastiandperei]

I think you are trying to "send results from a table" to another person (i don't think another reason to export to read only)

Did you try using "send bookmark by email"? It is in the Access Point interface, in "More" label...

[#6]

Hi Marcus,

The query is related to "Export to Excel" from accesspoint. Hence there will be no manual intervention.

As soon as the user exports data to excel from Access point, the generated excel should be in read only mode.

Any ways to achieve this ?

Thanks & Regards,

[#7]

Hi Sebastian,

No, it isn't for the transferring data from a table to another form.

As described in the above post, it is for end users who want to export data into excel from QV Access point directly.

Client wants it to be in read mode only.

Thanks & Regards,

[#8]

But if you really wish to have that functionality.

Then a macro is required.

1) Either create a export button separate with read only functionality.

2) For a chart, Copy the Image of the data and then paste it in excel file.

this can help:

community.qlik.com/docs/DOC-4315

community.qlik.com/thread/91136

qlikviewtips.wordpress.com/2011/10/17/is-possible-make-macros-that-run-server-side/

Thanks,

Angad

[marcus_sommer]

I would rather suggest to deny these export-functionality then you couldn't control it. Even if you have a write-protected file a user could copy+paste this content in a new file and throw the old one away.

- Marcus