Agnes,

[I don't see to many problems here.

the session object is non visual, but why should you use it? Use a Dataenvironment (class) instead. Just instantiate the right DE for the container. If you need to invoke the events/methods from the native DE you may use eventbinding.(I never use native DE because all my forms are classes (no scx) and will be instantiated via CREATEOBJECT, and form classes have no DE on the designer.)

BINDCONTROLS may be a help too.
The DE might be an property of the Container, so just instantiate the container, get the DE class from the prop and instantiate the DE, and SET .T. TO BINDCONTROLS .]

Your suggestion would save a lot of re-working the Session object to behvave more like a data environment. We have not looked at eventbinding at this point in the project. And yes, we also do not include a data environment in the forms that we design. We put one in temporarily to help with field names, etc., but we delete it out before we use the form.

The BINDCONTROLS solution sounds good. We'll have to look into that as that is exactly the methodoloy we were planning on using, that is, to add a custom property to the container and then instantiate the, in our case, session object at runtime.

Thanks for all of the good advice! We will certainly consider these suggestions.

Scott