On Mar 13, 2009, at 11:15 AM, MB Software Solutions General Account
wrote:
> I'm retooling the day job's report generation and had old notes from
> MBSS
> code saying that you recommended running SetMemory before running the
> REPORT FORM code. Was that right? I know it's good before queries
> (per
> your comments on the downloads page), but I wondered about before
> reports
> specifically.
It can't hurt. What it does is limit VFP to use only actual physical
RAM that is available at that moment, rather than the rosy virtual
memory numbers that Windows tells it is available. The reason I place
it before potential memory-dependent ops is that the user may have
opened/closed another app, or carried out some other action that
changed available physical RAM. Calling SetMemory ensures that the mem
limits are always the best at that moment.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
