Load Script as Button Click Event

[#1]

Hello,

I know Document.Reload() and Document.PartialReload()

Is there any possibility (Macros / Triggers / VBScript etc) to trigger / execute a data load as a button click event ?

So means: Any kind of load on demand concept ?

Let say first you load a general list:

and when selecting one data row, mored detailed infos should be loaded for a more detailed view.

And because of high data load, I only want to load those data, when selecting a certain row.

At the moment I only know reload() and partialreload() functions,

but are there further ways to directly load data after a button klick event or example.

thanks in advance.

[settu_periasamy]

Just a question. . How do you select data? After fully loaded, right?

So you want see only related data based on your selection. .

Maybe I'm misunderstood your requirement..

After selecting the data, you can use the option 'keep possible values', right? Instead of entire data in the qvw..only the related data should be there..

[oscar_ortiz]

If you are attempting to do this via a macro on access point this will not work.

You may want to look into direct discovery to see if that will help your situation.

[johnw]

I'm not sure I've understood, but in this example, there is a list box where you can select a single table to load - A, B, or C. Hit the reload button, and it runs a reload that reloads the selected table. The button uses actions to set a variable to the table then run a reload, and the script checks the value of the variable for which table to reload.

[#5]

Thanks John.

My problem is that we have many data (many rows to load), so I need to find concepts with load on demand.

I know in QlikView the best is, to initiallly load everything and then you have the relations and dependencies

But in our case: we first load data and then want to load further detail data only when is needed.

[johnw]

I can see a couple possible problems with your plan.

1. If it's too much data to load into memory, then it's likely too much data for a user to press a button and then sit there and wait for it to load. This isn't necessarily true, like if you loaded everything it would be 500 GB, but the basic data is only 10 MB, and then you're loading additional data in 10 MB chunks. You may be able to load 20 MB in a time frame that doesn't annoy your users TOO much.
   
2. If there's only one copy of the document for all users, I suspect bad things will happen with all those users each trying to do their own reloads of the same document. You could perhaps get around this by distributing a copy to every user using publisher.