Reload Limitations when accessing QVW via IE-Plugin

[#1]

Hi,

I have a QVW that is currently accessed directly via the QlikView Desktop, but I am moving this to QVS and providing browser access via the IE Plugin.

The QVW has a button which applies a user provided date range over the data set which exists on disk as QVD files. However, since the button tries to "reload" the data, this is not working.

I can see that other people have had similar problems and created .bat files or the like in order for the data to be reloaded from the QVDs, however, since the date range is provided on initial query of the data set, I cannot see how the current QVW can function without a significant-ish change.

I do not want to change the QVW as I did not write it. The only alternative I can see is to provide access to the QVS via the QlikView Desktop, which is undesirable given the user base involved.

Has anyone seen this and / or overcome a similar problem? Without creating a .bat file or complicated macro, it seems a little strange to me that the user is unable to query new data coming into the system in the form of QVD files, without the application being reloaded and saved elsewhere first.

[Peter_Cammaert]

This is what QlikView is (since a while): Analysis and Reloads are in different hands. This system has more advantages than disadvantages.

In QVS you can schedule frequent updates, you can assign document administrators to manage asynchronous updates, but end-user controlled full reloads are out of your league.

[kuba_michalik]

If this is something used by more than one user, and different users want different date ranges (and I guess they do, as otherwise there would not be much point for this reload on demand), then this approach would be unworkable anyway with a QV Server. There is only one copy of the document on the server and only one data set in that document, after all.

Why not just read in ALL THE DATAS and let the users select what they want instead of reloading on demand?

[#4]

Hi Peter,

Thanks for your swift reply. I am new to QlikView and I can see the sense in what you're saying; perhaps our QVW provides too much control to the end-user for browser-based access to be used.

I think I will stay with Desktop based access for now and look to develop the QVW at a later date.

[Brett_Bleess]

Luke, the only way to really do this would be to use an EDX trigger from the button object, here are a couple of links that will help you look into it, but I am not sure about passing parameters etc.

Using EDX in QlikView 11 - basic example

Using EDX in QlikView 11

Hopefully this gets you a new direction that might work out to some degree.

Regards,

Brett