Hi Scott -

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?


hth
-Stefan

>Greetings!
>
>We are developing an application that we want to function differently than anything I have ever seen in VFP.
>
>The main issue is that the application will have a container form, that is, a form that can contain from 0 up to maybe 20 containers on it. The decision on what containers will be included is made at run-time as the user security will determine this. The form itself will contain no objects other than the containers instantiated at run-time.
>
>Each container will be self-contained, that is, it will manage it's own data session and it's own data. In order to do this, we will be using a session object for each container to insure that the container has a private data session and maintains data integrity within itself.
>
>Since Session objects are not visual, they must be created dynamically at run-time as well.
>
>We don't seem to be finding much information in the Fox community about applications like this. Has anybody ever done anything like this?
>
>Thanks for any input you can provide!
>
>Scott Malinowski
>
>Product Development Manager
>Premiere Educational Systems Inc