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.
It's loading the whole script here (all lines uncommented) just fine and shows data, and leaves me to change values in fields (I'm using 10 SR4 x64 and 9 SR4 x64). You see that there are some known issues when INPUTFIELD works together with RESIDENT, and that may be the cause of the failure in your system.
I don't know what else to say, other than as you are already renaming fields, use just one INPUTFIELD line before the first load.
Can you plz once again try the enclosed qvw file, with changing the qvd file names which i've been attached in previous zip file. First reload the application with RTQMain.qvd, if execution is success then reload the application with 2.qvd. In both cases if execution is sucess then there is a problem with my qlikview version which i'm using.
Right now i'm using QV 10 SR3 build 9061.7. But you are using 10 SR4 x64 and 9 SR4 x64. Can you help me where can i download this versions.
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.
I know and perhaps it's worth writing an idea or opening a support case to see in what cases the null is such in QlikView when functions IsNull() or NullCount() or MissingCount() are involved and the differences between them.
I started doing the Len() thing some time ago for x64 computers, now I always do this, regardless the computer and the possible values (null, empty, blank, whatever).
.png "Miguel_Angel_Baeyens"){kind=avatar}
