>Hello,
>
>In my previous applications I never run into problems using the VFP's FORMS collection for all my form handling stuff. I was wondering why so often developers use their own form handlers to do form handling, when there is already a form handler available.
>
>Because I need to make a decision for our in-house framework I would appreciate comments from some of you that can give me some Pro's and Contra's for creating our own form handler.
>
>Thanks a lot for you time in advance!

The reason to use a form manager as opposed to the forms collection is more for what the collection doesn't give you.

1. ReleaseAllForms - cycles through all registered forms and releases them gracefully
2. TileForms - display all open forms in any way you want

You could create functions to do this using the _Screen.Forms collection, but it's just as easy (and more OO) to use a manager object to handle form related behavior.

HTH.