Omar,
I'm not sure I understand yout perceived severity. If you create a DE class with several CursorAdapter objects in it and then assign it for use with multiple forms, you can't delete one of the cursoradapters while editing the form.

Selecting DataEnvironment from the short-cut menu brings up the form's instance of your DE class. It does not bring up the DE class itself. If you try to delete one of the adapter objects, you will get a message saying something like "You can't delete a member object". This is how composite classes work. You could add code to the DE instance to issue a RemoveObject on one of the adapater objects at run-time but that won't affect the class itself.

However, if you close the form, open the DE class in the appropriate editor and then remove an object or two, you do affect the entire class and every form that uses it as the DE. But I don't think this is a likely scenaio.

But everything is up to you. If you don't feel comfortable using subclasses, then don't.

>What I was thinking of was that for example I had two forms using the same DataEnvironment class containing some CursorAdaptor classes I could delete one of them while working in one form without any problems but at the same time make the other form unusable. This kind of mistake is impossible when
>I use the default form DataEnvironment.
>