>>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

That's cool. It sounds like that would be good for general system variables, but I don't think it would be good for saving the grid settings. I don't want a bunch of variables for that.

Thanks,

-Michelle