oops forgot something - remember you can always RELEASE the public variables as the forms are released if you want to go that way - that also gets rid of the NULLS ...

>Ken,
>
>Thanks for the response!
>
>> try storing the refs in an array that resizes to the
>> number of open forms each time you create or close a
>> form - this, ideally, should be managed through an
>> global application object where the array exists as a property ...
>
>That's a good plan, but I still have the issue of this array being chock full of NULL references that never get cleaned up until the app closes...same deal as if I would use public variables. From the responses I have gotten so far, I guess I just shouldn't worry about all those NULLs hanging around, so I won't.
>
>I know a global application object is a good thing, and I have one, I just see it as overkill when it comes to organizing forms because in all honesty, my forms don't need organizing. I never do global things to the forms, and the forms don't need to communicate with each other. This application is basically a very loose set of screen-based tools that each do their own thing, and having to open and close forms through a mediator just sounds like a lot of work at this point...I generally just use CREATEOBJECT() and a Show, and I am off to the races!
>
>Thanks for your ideas!
>
>Joe Kaufman
>jkaufman@encompas.com