Hmm. Relative and Hard Coded are working.
I have the below:
SQL SELECT *
WHERE LastModifiedDate >= '$(vLastExecTime)';
WHERE NOT Exists(PrimaryKey);
Store * from Table into $(QVDPath)\TableName.qvd;
Thanks sri. I just did that yesterday but I am glad that it is going the right way to see suggest that as well.
What appears to be causing a lot of issues is the data being held in RAM despite the application being closed. Is there a Qlikview server setting that I have missed that would purge RAM do you know?
my Qlickview crashes after finishing the Upload file input, and requires more GB of RAM pinning the PC.
To resolve I formatted the pc .. QV re-installed and the problem is solved.
but a few weeks ago has reappeared ...
I initially thought some keys or join in the document, but this problem also occurs when I do a file linked some light
if I load the same QV by a colleague, in a few seconds the charge and update it, if I do it is locked
how do you solve it?
Actually I found it was due to a count distinct calculation on a table box caption title.
Weirdly, it seems to be calculated even when the whole table box is hidden and the user is navigating in other tabs.. When activating and showing the table, we can see that the title immediately displays the already calculated value when the table box itself is still being calculated. Removing it solved the strange behaviour of the application.