>>>OK - we need to talk..
>>>You are right: my command should... be:goform.helpdesk_maintform1.cmdenterquery.Enabled=.t....
>>>THIS WORKS AND I AM HAPPY!!! - but I want to understand what I am doing here.
>>>DO FORM updatcal name goform linked - what does this do? does it put my form
>>>in memory so I can reference the objects on the form. I always thought DO FORM
>>>calls a form?
>>
>>It's roughly the same as CREATEOBJECT() in that it creates a memory variable by which you can manipulate the form and its objects. It still runs the form, but you now have access to it from the outside.
>>
>>BTW, you might want to re-read Ed's posts. He's right about the correct OOP way of doing this.
>
>I try to do everything as "OOP-as-possible" but to do it that way wouldn't you have to save every form you create via the form-designer as a class in order to utilize CreateObject()? Either that or do it all through code including adding of all the objects and PEMs?

The way to handle non-class forms is actually the same as for class forms:
DO FORM frm1 NAME oApp.frm1 LINKED
and form reference saved in application object property (also you can use collection member here).