... and yet another reason to have have an oForms global object that holds an array of pointers to instantiated forms and that does the instantiation of forms (defined as classes, but I think this would hold water for .scx's as well) and from wich the load method of the intantiating form can draw its parameters.

Marc



>Another good suggestion. You could even have your form release the public variables after it had retrieved the values.
>
>>The best way is to have your parameters as properties of your applicaton object so they can be accessed at any point while you load the frame. Public variables will also work (please, no-one tell me why public variables are bad) if you have no application object.
>>
>>This parameter-passing problem is not unique to your design - most of us have slammed into it more than once.
>>
>>Barbara