>Peter,
>
>You are misinformed if you think the major reason for private data sessions is for multi-instance forms.

It's been mentioned quite a bit. I'm happy to accept that it not's a major reason.



>And you may be being presumptious if you think because you don't want two copies of a form open that your users will never want it. Ask the user that has to determine if two custoemr records are in fact the same customer if they would like to see both records at the same time on screen. I think they may answer yes.

I think they actually have that now. They would enter some of the common factors on the owners search screen. There they would see a browse showing all of the matching owners (two or more). They can then go to the owner's form and page-up/page-down between the exact records that were displayed in the browse.


>Anyway, back to the point, the major reason to use private data sessions is encapsulation. That is having a form object that encapsulates its data and function completely and independent of any other form that may be open at the same time.

OK.

>Other reasons are number of work areas available, using alias's that make sense instead of unqiue alias' so the work areas can be told apart,

This one I don't get. Could you elaborate?


>testing multi-user code an a single machine, when you get to DLLs and COM servers keeping one server form stomping on the data of another ...

I've been told that COM object have no UI. Confused again...

>The ability to allow multi-instance forms is simply a nice side effect.


Peter