Cache New VPEs on Start-up
By default, upon client start-up aPriori creates a local (or shared) cache of all VPEs. This process may take up to several minutes, depending on factors such as network speed and the number and complexity of VPEs at your site. Subsequent start-ups simply update the cache and are typically much faster than the initial cache.
Unchecking this preference causes aPriori to revert to older caching behavior, which does not retrieve and cache VPE data until you cost a part using that VPE. This older behavior sometimes introduces significant delays during the costing process, and also does not display progress messages like the newer, default behavior.
Note: See the aPriori System Administration Guide for information about options to clean caches.