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.

>>I am contemplating whether I should use the new DataEnvironment Class or keep using the default form Dataenvironment. I am in traditional C/S development. I think the pros for DEclass are reusability and subclassing but the cons that it is not as tightly knit to the form as before. The pros for using the default Form dataenvironment could be that it is easier to modify when you are working on the form.
>>
>>Any thoughts?
>
>Omar,
>Your con isn't true, IMO. You can design your own DE in a PRG or VCX and then use the new DEClass/DEClassLIbrary PEMs of the form to make the form use your class. When you select DataEnvironment from the form short-cut menu, you DE class is instantiated and you can set the instance level PEM values.
>
>HTH.