Kevin,

Really? An I-layer? I talked to you a couple years ago at your Costa Mesa class about that and didn't think you liked the idea. Now when I am coming around to your view, you are changing yours? Curious. ;-)

Actually in thinking about how to do the above work I came to believe the only way to add an I-layer to MM was to recompile the framework myself with each release, something I am reluctant to do. In VFP, since the inheritance is really applied at runtime, things work easily with an I-layer. How would it work in .Net? Am I right that I would have to recompile your framework to add my I-layer changes?

After two years of dinking around with .Net, C# and MM, I am finally knukling down and doing my first real-world project for a client. It is a fairly large one, too. So I would like to get it "right" the first time. (Well, you know, as right as I can.) Fortunately, I have at least a couple months of design time before I have to commit to coding anything, so I have time to figure out "little" things like this.

...Jim

>In the current version, the approach you have taken is best, but in MM .NET 2.3 we are providing an I-Layer for business forms that will allow you to make the changes you want at the level you need them.
>
>Best Regards,