Hi, David-

>I didn't mean to imply that single instance always equals modal, only that sometimes a modal form would be appropriate.

And I'm mortified that I so ascribed such a heinous opinion to you. *eg*

>What's the use case though for having lots of places that can launch a single instance form? Does it not mean that each form would have a different data context and therefore not really be single instance at all?

Okay, here's one. Two roads that go to the same town. Bet you thought I'd come up with a computer use case, huh? Actually, I mean that seriously. A client wanted the table maintenance form on two menus. One on the "adminstrator-only" menu, and one on a normal user submenu. The reason was that administrators would sometimes do maintance and they flat didn't want to have to look anywhere but their own menu.

Sometimes it is a data context change without any difference in the result.

>Modality annoys the heck (you may substitute a more intense expletive here if you like *g*) out of me, there's a dozen places in VFP itself where it goes modal when it darn well shouldn't and I've griped to the powers that be about it.

Yep. Love it when MS breaks their own UI standards.

>Some things are client dependent too, there are a whole class of users out there that are on the every form is modal end of the spectrum. *bg*

Yep. One's gotta serve the user base.