This is probably the fix to your problem (it took a little more ’digging’.)
-----------------------------
Comparing Large Projects:
Increasing Claim Digger Memory Settings When working with large projects, Claim Digger may fail to respond for long periods of time due to a lack of memory. Claim Digger uses the default JVM heap settings, which may not be adequate for the current project. The maximum amount of memory available to Claim Digger can be modified via the Windows registry.
Do not add this value to the registry unless the amount of physical memory installed exceeds 256MB.
Launch the Registry Editor and navigate to the following location: HKEY_CURRENT_USERSoftwarePrimaveraSharedExternalApplicationsClaim Digger.
Double-click the “Parameters” key and enter the following at the beginning of the Value data field: -Xmx256m Make sure you leave a space between “-Xmx256m” and the next character in the Value data field.
For more information about JVM heap sizes, please refer to the appropriate Java documentation.
--------------
By the way, whey you are ready to step-up to the Best, try Schedule Analyzer for the Enterprise (the real Schedule Analyzer.) The industry standard Schedule Analyzer for P3 is now available for P3ec. See
http://www.ronwinterconsulting.com/sa_main.htm for more on this.