Stefan,

[One important point might be that when each container manages its own dataenvironment, you'll have no native Load() event, i.e. no "early binding", right?
However, your description sounds similar to an approach that works in practice here, do you have any particular problems?]

Yes, you are correct on the native events. The session objects would need a lot of the functionality of the dataenvironment class and the containers would need a lot of the functionality of the form class. It's not an easy road to travel, that's for sure.

Dorin made a suggestion that might be the "easy" way to do this, I'll have to investigate it some more.

Problems? Yes, there are problems with doing it this way. One problem which we think we have solved is allowing the user to move containers within the main form. We are using the DBI controls and they have some quirks...translation, they don't work well with VFP is our conclusion. We may have to write our own controls like the explorer bar and the more sophisicated list box controls. Also, there is the issue of dealing with Session objects. Since they are not visual, you can not drop them on a container, nor can you drop a dataenvironment contol on a container. So, developing a strategy to manage and implement the sessions associated with containers is a real hot issue right now and remains a problem, if you will.

Thanks for your input. I appreciate it.

Scott