I use ASELOBJ() for builders that help configure objects that are already on the form, but I want to edit form properties and add objects programmatically.

The code listed below is being run in the click event of a button on my form builder window. After the new form is opened in design mode, the click code makes changes to the properties of the form and adds labels and textboxes based on the settings I selected in the form builder window.

This way I don't have to hack the SCX file. I could just use the form's object reference to change the settings and add objects. From what I understand, with ASELOBJ() I would have to manually open the form in design mode and then select an object in order to trace back a reference to the form.

I would much rather have the ability to edit the form as an object from any type of builder program I create.

But, thanks for the suggestion.

>David,
>
>Why aren't you using aselobj() to get a reference to the current design surface and use that object reference for your builder?
>
>This might also be tied to the new Dockable state of the windows in VFP7 I don't have it handy to test right now.
>
>>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?