A lack of RAM is quite probably not the reason for your issue even if your 200 MB file is compressed and takes nearly 1 GB on RAM. More likely seems that the file has a poor datamodel with circular loops, synthetic keys or calculations over island tables which prevents the opening or might need a lot of time (maybe hours) to open. In this case it would be useful to open the file without data (is a right-click option within the start-window of QlikView) and then to use the debugger with a reduced number of records (maybe 100) and to reload the application. Afterwards you could check within the tableviewer if there is any potential issue within the datamodel or any calculations in the UI.
A further check should go any macros/actions which might be triggered by opening the application.
Another potential cause could be that the file was developed/stored with a different major release of QlikView. In this case you should down- or upgrade the clients/server within your environment to ensure that all have the same release.
- Marcus
