Hello there,
when I do a refresh of one report I am getting the following error:
What is causing this?
Tomas
Date
Votes
2 comments
-
Jet Reports Historic Posts Hello Tomas -
Excel uses memory for two purposes: in storing the workbook itself and in processing the calculations involved in the workbook.
When operating in native (not compatibility) mode, Excel 2007 and the 32-bit edition of Excel 2010 are limited to 2 Gigabytes of memory for the Excel process under Windows (Windows memory limit). This 2 Gigabyte limit is a limit on the "Virtual Memory" address space. Virtual memory used by a process is actually larger than the "working set memory" reported by Windows Task Manager, but we can use Task Manager to get an estimation of what the report is doing.
While running the report, you could view the Task Manager Processes tab to see how much working set memory the Excel process is using. Assuming that the system has at least 2GB of RAM installed, as that number approaches the 1.1GB-1.6GB level, we can start to expect issues like this.
If that is the case, what can be done about it?
There are a few possibilities, but not all apply to all reports.
(a) If the report is having to search through some fairly large tables in NAV, having and using matching keys in NAV can be very helpful. In general, having a key in NAV that includes all the filters being applied in the NL(Table) function (or, obviously, changing the the order of the filters in the function to match an existing Key in NAV) can improve speed and can decrease the amount of processing Excel has to do.
(b) The above method seeks to limit the amount of information Excel has to examine. Obviously, another option lies in limiting the amount of information Excel needs to store.
This would involve filtering the report so that less data is returned. The report could be broken up to examine a smaller range of accounts (running the report multiple times with different ranges to get a total) or a smaller date range to limit the size.
-HP -
Jet Reports Historic Posts One thing to try - if the table key wasn't included in this report, add it.
This could resolve the issue for you.
Please sign in to leave a comment.