>>There are lots of reasons why a user might want to view more than one record of a given table at the same time. This means multiple instances of the same form. Private DSs are a natural way to handle this. It would be difficult at best to support this - especially if you're going to use buffering - without using private DSs.
>>
>>I would suggest that a general purpose framework should support this functionality.
>
>
>I agree that the private DS is the more general approach. I would like to find a way to support the functionality that I described (integrated movement) while allowing additional independent views as an option.
>
>In the first case having all of the forms related to a single DS seems much more efficient.
>
>Peter

There's no reason you can't have it both ways. Use default & private DSs where each make the best sense. I just wanted to point out that a general purpose framework should support multiple form instantiation. I imagine that could somehow be supported through the default DS, but it would be a lot of work.