Mike,

He has the property already in his classes. All he needs to be able to do is cast the various classes to something they all have in common so that he can access that propery ... hence, an Interface is the perfect solution. That's the kind of things that Interfaces are designed for.

~~Bonnie


>I know what you mean - sometimes I wish I could use code from two different classes too. There always seems to be some way around it.
>
>"Multiple inheritance" is allowed in C#, but you can only inherit one class. I realize you know this, just wanted to be specific. You can inherit from multiple interfaces. I'm sure you know this too <s>, and Bonnie mentioned that.
>
>The problem, I think, is that you don't want to implement an interface, you want to use existing code. You can't define code in an interface, just the declaration for its members, so an interface might not be your solution. Then again, it might.
>
>What does your BasePath property do? I'm assuming it's more than a getter/setter. Guess what I'm thinking is it might be possible to create a static class/method that takes the form as a parameter and returns something useful.
>
>Mike