>Paul,
>
>By the session object, do you mean the cDataSession property of the business object? If I could use this to create private datasessions for my lookup objects, that would solve my problems. BTW, is the idea of the business object cDataSession property to remove datasessions from the form?
>

I don't think you can use the cDataSession property that way. If I remember right, I think it's just a generic reference to the type of object that will get created when the bizobj creates it's data environment. I also think it keeps a reference to it in a property, so you're limited to one. Maybe this is a case where you would use multiple datasessions in your bizobj?

Another idea might be to create a barebones bizobj that uses your view for the state lookup in it. Drop it onto your cListObjEditForm. I (think) it should use it's own private datasession, even though the form is using the default one.

It kind of seems like the framework should be checking to see if an alias is already open when it is opened. If it is, it should leave it open when it closes. Of course, that may be a big performance hit to check that.

Yes, the main idea behind creating a datasession there is to remove it from the form. The data is really the responsibility of the bizobj, not the form, so that's really where it belongs. Also, in the case of COM, you need each bizobj to have a private datasession - otherwise your COM objects might stomp on each other by sharing the default datasession (multiple instances of the same bizobj would definitely be a problem there!).