I don't think it's very significant either way. I do my own DataEnvironment either whether form or class.

IF IsForm
   DO FORM (m.FormName) WITH &FormParameters. NAME oForm LINKED NOSHOW
ELSE
   oForm = CREATEOBJECT(m.FormName, &FormParameters.)
ENDIF
oForm.Show()

The main benefit is you can subclass and CREATEOBJECT doesn't pull in a DE. (which may be a disadvantage for you). You can always make it a class if you want later. I do both and I don't really care either way.


>Having had no formal training in VFP I find that I use "do form" instead of "create object". However, a lot of the code that other people have written uses "create object". Can anyone briefly show me the benefits of create object over do form
>
>Alan Wyne
>Rollpak Corp