Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Script execution fail.

Hi

When i'm loading my qvw file with updated qvd file i'm getting the script execution fail error message. Can anyone help why this error message shows when qvd file is updated with new data.

Here i'm attaching zip file which consists of two qvd files with less data and one 1 qvw file. can anyone please check this and help me how to overcome this. I'm trying from long period on this but still i'm not able to resovle this issue.   

1 Solution

Accepted Solutions
Miguel_Angel_Baeyens

Hi Jacq,

In the first line where you load all fields from RTQMain.qvd or 2.qvd, comment that line and set "*" instead (to load all fields). Then run the script. That should work.

Actually, RTQMain.qvd loads without problem. 2.qvd does create an error as you mentioned above. Changing that line to "*" works just fine.

If you still need the file reloaded, let me know.

Hope that helps.

Miguel

OK: forgot what I said above (I'll leave it anyway). The issue happens with the IsNull() function. Leave it all as it was in your original upload, but change your WHERE clause to this in each file you load:

While Len(FieldValue('BCShotHoldPressTime2R', IterNo())) > 0;

Using Len(field) > 0 instead of Not IsNull(field). IsNull() keeps behaving wrong in different computers with different data, and usually with x64 architecture computers. It's not the first time it happens to me, and I've read several posts in the QlikCommunity in this regard. It's not documented and likely have to do with how QlikView deals with the data source (in some cases and "empty" value is not a "null" value or a "blank" value).

Functionality of both is the same. If the length of a given value is zero, then we can assume the value is null. It doesn't degrade performance and will work fine with bot x64 and 32 bits systems.

View solution in original post

17 Replies
Not applicable
Author

Qlikview guru's please help me on this..

llauses243
Creator III
Creator III

Hi ,

Your case is very interesting, funct with V9, no funct with V10 ¡¡

Moreover your script can be more simple using SUB in script

This will continue ...

Good luck, Luis

Not applicable
Author

Luis Laura,

Thanks a lot for your relpy. But i'm not able to understand what u r saying for me. Is there any solution for this. Right now i'm using SR3 qlikview 10 version.

swuehl
MVP
MVP

jacq,

I think the problem is the multiple use of

INPUTFIELD MinIMM,MaxIMM;

Try removing all occurences except the first. This did the job for me (QV10 SR3).

Regards,

Stefan

Not applicable
Author

Ya your right. I had tried what you said but, still my problem is not solved.

Miguel_Angel_Baeyens

Hi Jacq,

Even with the inputfields in place (that actually accept as many fields as you want, even wildcards just fine), the reload finishes all right.

What error are you getting and when? Did you do a debug load to see where the script stops?

Hope that helps.

Miguel

Not applicable
Author

Miguel,

I'm getting the error message as "Execution of script failed. Reload old data". This error comes when i reload qvw file with updated qvd file.

I've seen debug mode also to find where the problem is. It is executing entire script without any problem, I can also able to see "---------Script Finished--------------". But when i Click on Close button it shows the above mentioned error.

Miguel_Angel_Baeyens

Jacq,

Is there any chance that you are using QV 10 SR3 build 9055? That release was updated with QV 10 SR3 build 9061. If so, upgrade and it should run all right.

Apart from that, is there any other piece of code in your script in addition to the application you have uploaded? (There are lots of lines commented that may be causing unwanted synthetic keys, concatenations or so).

Hope that helps.

Miguel

EDIT: In addition to the above, the Release Notes for SR3 and SR4 read:

Inputfields are not compatible with joins or resident loads. The reason for this is that an inputfield must be read one time and one time only. Once the inputfield is read it is added to an inputfield table and this table cannot be tampered with. Joins affect the table and for that reason inputfields are disabled when combined with joins. Resident works slightly different but it also affects the inputfield table and it is disabled for the same reason.

Release Notes for SR4 have one bug corrected that reads:

41848 Document Reload Fails with Inputfield

Whatever that means without futher details, upgrading to the SR4 may worth the effort to check whether that solves your issue or not.

Not applicable
Author

I'm using QV 10 SR3 build 9061.7. Ya i'm executing the uncomment code also.

Let me explain why i developed that:

I've around 300 fields. The end user wants to see Min and Max of those fields and he want to choose his own fields by changing the Min and Max values.

For Eg:

A,     B,      C,     D  are the fields

Now he want to see all this in one group along with min and max

Group     Min     Max

A           10       20

B           12       34

C           0         6

D           1         5

For this i've taken one listbox along with expression to display Min and Max. When he choose A i'm allowing to change min and max values through the table box.