Ken,

> if you resize the array each time you add/delete a form,
> you won't have any left over nulls - the array will always
> have exactly one "row" for each form. Again - this can be
> handled within your app object with wrapper methods
> like "Addform" and "removeform"

Yes, this would work, except I have no idea when the form get's removed, unless I place code in my form classes release event to do such a thing. I was trying to avoid having to control the releases from the form's side of things, as that is invariably more complex than being able to just summon the silly thing without a reference in the first place. DO FORM can do it (well, not really, it creates a reference, but unless you use LINKED, Fox leaves the form up even when the reference goes out of scope...that is _exactly_ the behavior I desire), I just wish there was a way with CREATEOBJECT()

Adding removal code to the form objects may be the route I will have to go, but that has complexities as well since I give an essentially random reference name to the form's when they are created, so I would either have to store that name on the form or use the app object...I don't care for either idea.

Thanks,
Joe Kaufman
jkaufman@encompas.com