>>Hi JimB,
>>
>>There is one "gotcha" with _SCREEN.ActiveForm, I thought might be worth mentioning. If you use the Microsoft Toolbar 6.0, the _SCREEN.ActiveForm object refers to the toolbar and not the form. The only workaround for this that I've found is to use _SCREEN.Forms(1) instead.
>>
>>PS Have a great DevCon. Sorry I can't be there.
>
>George,
>
>Yeah that's true, but Forms(1) ony works if the active form is the first one that was run. The best all around solution is to use a framework that tracks forms for you.

JimB,

Hmm, my experience has been that the collection is re-ordered as a new form is brought to the front. Admittedly, I've only tested this in the design mode and not production as of yet. However, it seems as if the indices represents the current Z-Order of the forms collection, and not (at least in design mode) the creation order.