I hope your do realize that that renders the section access useless, in which case I would find it better advice to remove the section access statement form the loadscript. Depending on use case, even better would have been to make sure that whoever should be able to do a full reload with full data also has the correct access rights to the data.
I had similar problem. Disabling Initial Data Reduction Based on Section Access option as suggested by Martin Mahler works but was confused when initially I never had this problem on the original document I was working on. What happen is that I made some changes to the original document, reload it and when I clicked the save button, QlikView displays a Save As dialog in which at that time I figured I want to change to a different name in case I needed back the original document. So I did. Then I close it and when I reopened the document (with the newly saved with different), the last data doesn't seemed to be there, changes made to the objects (resizing/rearranging their position) are still intact but the latest reloaded data wasn't.
Can somebody would give some insights to this matter? Any precaution steps to take to avoid similar problem occur again?