>I see more of your problem now, Nadya. However, could this code be added to the instantiation of each container module? Then it would run at the time the container was instantiated instead of when the form was initialized.
>
>Barbara
>
Hi Barbara,

I'm thinking about it too, but I'm not sure. Currently it's done in one time - in the Form's Init. E.g. each saved configuration is run from first seq to the last seq number. If I'd like to separate these processes, I have to pass seq numbers (start and first) to the restoration method and invoke it for each container Init method. Also these cmdlines now should use relative notation instead of full notation. It's a complicated problem, but at some point with the help of my colleague I'm going to implement this idea.

Currently, for my regret, we freeze this application in its current state for the first Release.

>>Barbara,
>>
>>This logic (invention of my colleague) saves the current state of the form in the MetaFile. This MetaFile basically consists of three fields (if we would not count modidate and notes): FunctionID, Seq & CmdLine.
>>
>>This is an example of cmdLine:
>>

m.cmdr_arg1.parent.pageframe1.pageLoc.Container1.conZip.btcc_zipcode.Container1.setall('enabled',.t.)

>>
>>IOW, form object will have full notation here. Now, imagine, that I will delay instantiation of this object, this line of code will bomb, because the object doesn't exist. Therefore it would tough and painful process to incorporate this great idea into this existing application.
>>
>>I tried this idea today on another quite simple form, but it did not work properly. First problem is that there are mutual page objects dependencies in the form's code, and the other problem, that this form uses related tables instead of views. So, my changes didn't work.
>>
>>If I would start fresh form, I would definitely use this idea, but for the old forms it's a hard process to change the existing code...
>>