>Snip...
>>Hello Again,
>>
>> I found my problem. The forms in this case are based on a class contained in a vcx then turned into a project form using New/New Form and dropping the form class from the toolbar. Problem is, I forgot to remove the formset after removing the default form1 from the form designer. So, while reading about PARAMETERS, it makes the statement "It must be the first executable statement in the called object". Since it actually is a formset, the formB Init is not first,
>>formsetB Init is first. Just another case of proceduralitis on my part.
>>
>>Thanks for the tip on passing the THISFORM reference.
>>
>>Eric Kleeman
>Eric just another tip, you could pass thisform to pass a reference to FormB, but the reverse needs "name" clause.
>

>* Case 1
>*formA
>do form formB with thisform     && Just pass thisform ref to formB
>...
>* FormA is clicked or called from formB - formB still open
>* Want to click or change a value in formB - there is no reference to formB
>
>* Case 2
>*formA
>do form formB with thisform  name "formBReferenced"  && Pass thisform ref to formB and also have a reference to formB
>...
>* FormA is clicked or called from formB - formB still open
>formBReferenced.text3.value = "Newvalue"    && We have a ref to formB now
>formBReferenced.cmdDummy.click
>...
>do form formC  && Another form is called
>*FormC
>formBReferenced.text3.value = "FormC changed this"  && Even another form has a ref to formB
>
>

>Cetin

Cetin,

I am going to use your suggestion but just one more hangup,

I am going to , DO FORM formB WITH THIS , from formA then from formB I need to set a property in formA. When I try to reference formA in KeyPress of formB.list1, it says it cannot find the referenced object. I recieve the reference via formB Init as a parameter paramB. Then , paramB.textbox.value = xxx , in formB.list1.KeyPress does not find the formA.textbox object.

Can you explain this referencing further?

Eric K.