>>>I am working with a very large, complex, convoluted application. One thing we have a lot of problems with is called programs causing problems for the caller. What I am looking for is a robust method of saving the environment (open work areas, index orders, record pointers, FoxPro SET values, etc.) upon entry of a called program and then restoring it on exit.
>>>
>>>CREATE VIEW filename, then SET VIEW TO filename seem to offer a simple built-in way of doing so. I have not used them. Do they really work?
>>>
>>>If not, can anyone recommend some downloadable code? I have seen code which does this but can't lay my hands on it at the moment.
>>>
>>>Thanks in advance!
>>
>>Found this Re: How to save all SET settings? Thread #947972 Message #948032
>
>Naomi, not to be harsh but this is a perfect example of you rushing to find a link to send someone instead of really trying to help them solve the problem. That class does not come anywhere near achieving what I want. I want the whole environment restored to where it was at the time of the call, not just SETtings. That's what I said in my post. No stars for this reply.
>
>Anyone? Bueller?

Well, I thought it's a good class that should lead you to the right direction. All other messages I viewed on your behalf trying to find a good information were pointing to the same approach you already listed in your message. Saving order and, aused for used work areas, recno() for record pointer in the area could have been addition to a big part of already done in that code I sent you.