Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
.ini files
Message
From
30/10/1998 09:49:38
 
 
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00150938
Message ID:
00152782
Views:
30
>Ok, you're crazy. :)
>
>What's a ".MEM" file?

It's a file created by the SAVE TO coomand which contains memory variables and their values in an internal format. Once saved to a .MEM file, the variables can be recreated with their values restored as PRIVATE variables (visible downward, but not upward or globally.) Take a look at SAVE TO to see what's involved in selecting the variables to be included in a .MEM file; it's most useful if the saved variables all share a common root name (ie they all start with the same name, so that they can be masked for inclusion with the LIKE clause. AS an example:

SAVE TO MySysVar ALL LIKE ?SysParm*

would save all variables visibile to the current process whose name match the wildcard mask, so that if I had variables:

cSysParmUserName
nSysParmAnswerToEverything
cMyUserName
uRandomVar
gcObnoxiousLegacyGlobal
nSysArgument1

it would save the variables cSysParmUserName and nSysParmAnswerToEverything and their current values to the file MySysVar.MEM

You could later restore these variables as PRIVATE variables by issuing the command:

RESTORE FROM MySysVar ADDITIVE

>
>Thanks,
>
>-Michelle
>
>
>>Hi again Michelle.
>>
>>Call me crazy, but I still go around thinking about our little topic here. Even though we pretty much see eye-to-eye on it, my brain apparently doesn't take that as no stopping sign, so here's the latest from my "top floor":
>>Have you considered creating a ".MEM" files instead of ".INI"s? That would, of course, have you back on a file per user, but I suspect the performance would benefit as well as it would be a simplier approach for you to deal with. Maybe store an array ga< UserLoginID > with all the stuff you need for those grids.
>>
>>Just something to chew on...
>>
>>>>>Good point. I guess I'll go back to a file apiece.
>>>>>
>>>>
>>>>Not exactly what I was aiming at. Reading the INI file doesn't take that long that user might get frustrated waiting on it. I just suggested you put reading the file in a time limited loop, in case the file is used by someone else. That will solve the problem. Guard yourself from that, and you'll be fine.
>>>
>>>That's true.
>>>
>>>Thanks,
>>>
>>>-Michelle
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