>>I know the problem is probably with the Docs, but using the Session class to create a default data session does not make sense to me. A default DS is created when VFP or a VFP app launches. Why would I create something I already have? I would think by definition that Session means a new, and therefore private, DS.
>>
>>I have already made good use of this class in setting up a private DS for my MAIN.PRG for setup work. That way I do not have to step on anything in DS 1 that I want generally available.
>
>I agree, Mark, for the most part. However, we've been in this business long enough to know that just because we can't think of a reason to have something like this, doesn't mean that there isn't one. The curious thing to me is that it's documented the way it. It's new documentation (they didn't lift it from the form documentation on the DS). Perhaps the intent was to allow the setting and something happened that changed their minds. I know, but I'm hoping that Randy Brown will fill us in.


In my case, the reason for wanting a default data session is typically as follows:

Our reporting class typically creates a private data session which manipulates the data it requires to print/display. In some cases, a form or business object has already done all the required data manipulation (in a private data session). Being able to call a subclassed reporting object with a default data session (ie the private data session created by the calling object Not the FoxPro default data session) seems a logical and sensible requirement. It has the benefits of allowing the report class to open (and close) any addition tables using a consistent developement interface.