That sounds much tidier than what I do (which is hide them behind other object s on the form such as grids etc. This makes them a pain to find when I want to access them.)

Be nice if VFP had a button that either made the bizobs visible or invisible as required.

I will go udate the suggestions for VFP document now (My saying something like this usually leads to a flood of replies pointing out that such a button has existed since VFP -1.00 )


>Hmmm.... at first this didn't make much sense because I had to instantiate thos bizobjs anyway, but then what I could do is create a super-class that would encompass groups of bizobjs and do all the magic through its init() method.
>
>This would remove the clutter from the form, but I would have to refer to my bizobjs instead of by "Thisform.mybizobj" as "Thisform.mycontainer.mybizobj".
>
>Food for thought!
>
>Thanks!
>
>Alex
>
>
>>Yep thats pretty much what I was thinking, however I am a bit uncertain as to if you should be putting them in the load event or the init event of the form.
>>
>>I guess that depends on what your objects do as regards data.
>>
>>I wonder where in the event sequence VFP instatiates them when you just drop them on the form, obviously that would be the right place for you.
>>
>>>>Hmm why don't you just instantiate them from within your init event or something.
>>>
>>>Well, that doesn't seem like a bad idea either, thanks!
>>>
>>>
>>>Just to make sure I understood, your proposing to do something like this within the init of the form:
>>>
>>>o1 = createobject("patient_status_bizobj")
>>>o2 = createobject("Documents_requested_bizobj")
>>>etc etc etc, right?
>>>
>>>
>>>>Or am I missing something here, which is usually the case:(
>>>
>>>Welcome to the club ;-)
>>>
>>>Alex