If you want to play it cheap, you can call your startup program from Form's load.

Anyway, I should be studing a different subject right now...

>I created a 'startup' program many moons ago and have left the 'sets' except the changes necessary when changing VFP versions.
>I agree that creating a class is the way to go.
>I will probably try it tomorrow ... been a long day and I am starting to fade fast.
>
>Thanks once again.
>
>>Most of them scoped to DS. You can check for some, which you're not sure. Or you can have a form class and do it once :)
>>
>>>Nadya,
>>>
>>>No, it wasn't. But it is now. Thanks.
>>>
>>>I have about 70 'sets' in my startup program.
>>>Should I be going thru the help for each to see which are scoped to the current data session and then duplicate that code in the called form?
>>>Or, is there a simplier way?
>>>
>>>TIA.
>>>
>>>>First check the obvious - is SET TALK OFF in the second form's DS?
>>>>
>>>>>I have a form (form 'A') which has a page frame with three pages.
>>>>>On the 2nd page, about 1/2 inch from the top, on the left hand side, are two controls - a label and text field.
>>>>>On this same page is a command button control that does a 'Do form' (form 'B') which has its own datasession.
>>>>>When I thisform.release() on form 'B', form 'A' reappears on the screen. Page 2 still appears to be the current page. However, the top 20% of the 2 controls mentioned above * also * appear just above the tab name for page 1.
>>>>>If I click on the tab for page 1 or page 3, the strip disappears. Same if I return to page 2.
>>>>>
>>>>>Have I missed setting a property before invoking form 'B' or upon its return?
>>>>>
>>>>>TIA.