Actually the "right" way of solving this would be to turn off error checking that terminates the script at these critical points in the load script. Then you will also have to supplement with additional checks to be able to catch the errors that might occur.
This can be done by using the ErrorMode variable and setting it to 0. Most - but unfortunately not all - errors can then be caught by checking the dual-valued ScriptError variable immediately after the statement that might fail. In your case that would be something like:
STORE [a_table] INTO "SomeQVDfile.QVD" (QVD);
Unfortunately the last few or maybe many of the latest QV 11.20 Service Releases including SR12, does not handle this as it was originally documented/designed. It goes into a "General Script Error" instead of continuing the script and letting the script check the ScriptError.
This could SHOULD have worked in QV 11.2 SR12:
Set ErrorMode=0;
STORE [mytable] INTO "path_that_doesnt_work\myTable.QVD" (QVD);
vStoreError = ScriptError;
IF vStoreError > 0 THEN
// some sensible error handling - reporting the acutal issue...
// this code will never be reached since STORE when it gets into some kind of trouble with what
// is after INTO just exists the script with a (almost) meaningless error: General Script Error
ENDIF;
The good news is that Qlik Sense behaves as it should. The better news is that QlikView 12 beta also works
as designed and will respect the ErrorMode 0 instead of failing with a general error. So hopefully this "fix" will also be a part of the IR (Intial Release) of QlikView 12 which is due pretty soon it seems.
Anyhow there is the option to do defensive coding by checking for the existence of a particular file by checking the filesize - which you do have a function in QlikView for.
