07-18-2008 05:02 AM
07-18-2008 09:48 AM
Hi Venkatesh Murthy,
After you've run into this error, check the Windows Task Manager to see how much available RAM you have left on your PC. My guess is that you just need to buy more RAM or close down some other applications (Lotus Notes?) to free up more RAM.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
07-19-2008 12:50 AM
09-25-2009 07:44 AM
09-25-2009 08:50 AM
Update.... According to Windows task manager I have 3GB of free physical memory and DIAdem is using 305kB physical and 370kB virtual when the error occurs. It doesn't appear to be a windows limitation.
What else could it be???
09-28-2009 03:42 PM
Hi Siriusly,
Would you be able to post your VBScript and your data files so we can reproduce this problem and begin to debug it? This 300 sheet issue has popped up a couple of times now, but it is not a hard limit-- I have created over 1000 sheets before with no problems. It must be something specific to your reports. Do you use 3D plots on any of your 300 sheets (they tend to be memory-intensive)? Based on your latest data it does sound like we can abandon the idea of an OS memory limitation, but there may still be a DIAdem-imposed memory limitation that results in 1000 simple sheets being OK but 300 memory-intensive sheets being too much.
Brad Turpin
DIAdem Product Support Engineer
National Instruments
09-29-2009 07:54 AM
I have uploaded the Script and report layouts to the ni.ftp site (300 Page Issue.zip). You must load your data manually before running the script. I have password protected the zip file and I will need to email you the password. The report is basically all text objects and not really conventional "data"
Thanks for the help Brad
09-30-2009 10:28 AM
Hi Siriusly (and others),
R&D has confirmed that DIAdem 11.1 introduced a memory fragmentation issue that is behind the behaviour you are seeing here. As far as we know this problem did not exist in any previous DIAdem version. We also hope to remove it from subsequent DIAdem versions. For the time being, my recommendation is to load and configure each REPORT sheet separately and append them to the PDF file by setting the optional second parameter of the PicPdfPrint() command to TRUE. This will mean that you only have 1 REPORT sheet loaded in memory at any given time, so it should sidestep the problem in DIAdem 11.1.
Brad Turpin
DIAdem Product Support Engineer
National Instruments