Yes, this will work if I convert my template SCX files into form classes and use the "AS classname FROM classfile" parameters.

I still would like to know why the other functionality was dropped in 7.0. With it I could create a series of builder programs that would operate on any form I had open in design mode or (even multiple forms).

Programatic access to the design tools is a great feature! Thank you for suggesting this alternate method.


>Here's code that might work better for you:
>
>

CREATE FORM (myform) NOWAIT
>nObjs=ASELOBJ(aObjs,1)
>nIdx=0
>FOR i = 1 TO nObjs
>   IF UPPER(aObjs(i).Class) = "FORM"
>      nIdx=i
>   ENDIF
>ENDFOR
>aObjs(nIdx).Caption="I can change the form's caption in developer mode!"
>

>
>Note use of the ASELOBJ function.....
>
>
>
>
>
>
>
>>In VFP 6.0 SP5 (or SP3?) the following code worked:
>>
>>MODI FORM (myform) NOWAIT
>>
>>FOR ln = 1 TO _screen.FormCount
>> IF _screen.Forms(ln).Name = "form1"
>> lo = _screen.Forms(ln)
>> EXIT
>> ENDIF
>>ENDFOR
>>lo.Caption = "I can change the form's caption in developer mode!"
>>
>>I could run this code from within an APP, EXE or PRG and use it to modify the form in design mode. But in VFP 7.0 the form being modified is not shown in the _screen.Forms collection.
>>
>>Was this an undocumented feature that was taken out of VFP 7.0? Will it be in VFP 8.0? I was able to create several form builders using this technique and they have saved me hours.
>>
>>What happened to one of my favorite features of VFP?