>I see three options - have the stateless component do it's usual work of setting up tables before launching pivot wiz (in either default data session if that's even possible, or in a separate data session). If I go with the default component doing the work separate from my application's default data session, having it pass off a session object to the piv wiz is probably my best bet. My third option would be to roll another stateless component right into MyWiz.app and make it completely self contained.
>
>I'm not sure at this point where I want to go... the point of my original message was to rule out the one cludge-like possibility to make the whole scenario simpler. That one possibility is "can I even get a separate MyWiz.app to see what's in my main applications DS 1"

Why not? I have a luncher.exe that has a Do ['MyApp'] at the end of the prg. Then in MyApp.App, I have a menu option to call my Reports.App. Both of these apps can use the default DS [DS 1], or their own. Actually MyApp is in the default DS. Reports.App is controlled by a generic form to handle report selection and uses a private DS.

Otherwise, I use properties of my oApp object to keep up with what DS I want to be working in for some of my app class methods. If oApp.nDataSession is zero, methods that look for this use the currently selected DS. Otherwise, the method code switches to the DS value found in that property [and switches back to what it was when finished, of course].