Hi, Robert,

The approach that Danny provided should work fine for your situation.

At the risk of sounding like a 'purist', it does bend the concept of decoupling the interface from other elements. In some situations, it's not really an issue.

However, suppose you wind up developing some type of 'spin-off' application, one that provides a subset of the current functionality. Quite possibly, that means pulling out some of those objects and elements, which means possible duplication.

Consider further that your 'spin-off' app doesn't have an interface - it's a service, or some other type of non-visual app. You can't 'fall back' on an MDI parent. So what may seem expeditious now may not seem as attractive down the road.

However, if you take those elements/strings/datatables that you know you're going to use in different parts of the app (and maybe other apps) and define them separately, you may make the development effort down the road a bit easier if you decouple everything up front.

Kevin