Hi Kevin (again),

[This thread should be retitled "wizard classes" but UT won't let me]

It's late (well, 9:30pm but I'm tired..) and I'm not feeling particularly good at stringing words together, so if I insult any of your code be sure I don't mean it... I think you may be planning on solving this one anyway

Are you going to derive mmWizardForm from mmBusinessBaseForm? Because if you are I'm going in and modding the 2.4 source code now! All the mmXYZ controls depend on GetParentBusinessBaseForm() working and on a wizard they don't!

In particular, things like mmDataGridView.GetCurrentRow always returns null, not because there isn't a current row, but because the code short circuits out after looking for (form is mmBusinessBaseForm).

It looks to me like mmFormManager.GetParentBusinessBaseform() needs to be looking for an *interface* not a superclass. It would have been nice if I could simply subclass mmWizardForm and add in ImmBusinessBaseForm - unfortunately it doesn't work. Actually the interface should probably be "ImmBizObjRegistry" or something.

I could just write my own wizard framework, which is what I thought I'd do when I originally drew up all the UI design the client signed off on, but it would be so much nicer to use the classes you kindly provide.

I need to get a demo of this working tomorrow morning, so for now I'll go into temporary 'hack' mode and either write my own temporary GetCurrentRow implementation - since I already know EXACTLY what bizobj to look at - or maybe I'll be able to fix with the bizobj-aware-usercontrol trick that you posted a few days ago.

oh, and that bug with exactly two pages .. you might have noticed that there's a related bug with only one page (next is enabled, finish isn't). And then btnNext_click itself doesn't check that the WizardPages collection has enough items to advance to a next one, and crashes.

Cheers,
Walter