Load script skips a table during the script execution process
I have been having an issue that I couldn't figure out the root cause of it. I am trying to load two tables VM_CLAIM and VM_MEMBMTHS, and they both reside in the same database so that the one ODBC connection is used. Also "Force 32 Bit" option is checked.
What happens is that the first table VM_CLAIM gets loaded, but the second table VM_MEMBMTHS doesn't. Almost QlikView skips the second table for some reasons. I checked the availability of VM_MEMBMTHStable in both SQL Server and another BI tool, the table runs perfectly.
Here is a screenshot of the script execution progress window:
There are two different tables in the load script:
I also checked if the tables are being concatenated, and there is only one common field in both tables so I don't think it is a concatenation issue.
If anyone had this issue and resolved it, I would appreciate your feedback.
Re: Load script skips a table during the script execution process
It is commonly known (very recently by me as well, although I've been fighting them for some time now) that Preceding Loads should be used for doing just minor column and value manipulations. As soon as you start doing extra filtering (or GROUP BYs) you may unexpectedly run into trouble.
You can continue doing what Andres initiated. Add the next Preceding load and see what you get. If that doesn't work, try a conversion into successive RESIDENT LOADS. That should work in any case or will produce at least proper error messages if it doesn't.