Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Application Memory Footprint
Message
From
24/08/1999 13:31:02
 
 
To
24/08/1999 12:32:59
Chris Rahmes
Riverbend Nursery, Inc
Riner, Virginia, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00257117
Message ID:
00257193
Views:
29
>Jim,
>
>When running on a system with 32 MB of physical memory and NT 4.0 workstation as the O. S., I have very little memory left over. Yes, it is causing me a performance problem!
>
>If .dll's were built instead of .app's, or if everything was compiled into the main .exe instead of multiple .app's, could the memory usage be lowered considerably?
>

Nope. VFP's memory manager can (and will) use any and all memory available to it for an application, regardless of whether it's compiled into an .APP or a .EXE (the only difference is how the VFP runtime itself gets started up; it's the same runtime regardless of how the app is compiled unless you're running under the development version, in which case, it's the same development engine being fired up regardless of whether it's compiled to an .APP or an .EXE file.

This sounds more like a problem with how your NT system is configured than with VFP, though - even if you have only 32MB of RAM available, your can (and should) have more memory available as virutal memory throguh the swap file, and when the VFP app isn't active, it can (amd will be) paged out of physical RAM.

>Thanks
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform