Thanks for the response.

The problem is that in the dataenvironment init and beforeopentables methods, the form is not available, i.e. if you put thisform in a watch window, it gives "expression could not be evaluated". In fact there is not much of anything available or accessible. I was having some problems due to basing my report environment off the app environment class instead of the app report environment class. Fixing that allowed me to get further.

The report is already using the forms private data session, so that isn't an issue here.

Other than referring to _screen.activeform in the report dataenvironment init, I've got it working to mey satisfaction at this point. We'll see how it goes as I get further into it.

If you are not using standard MM reporting options, what sort of approach did you take?

June


>>How do you pass a view parameter to a report, with out using a form in the dtaaenvirnment beforeopentables method?
>>
>>I've got a form where I want to have a button on it that prints a one page report for the currently selected record in the initialselectedalias of the primary bizobj. I dropped a copy of the (subclassed) creportsobj on my form, and set up a view and data environment for this report. I know what I want to specify for the view parameter, so don't want to call up a form to make the user re-select what they've already selected on the existing form. I added a report variable to the report that is my view parameter. How do I set this so that it is there when the requery happens? Thisform is not accessible in BeforeOpenTables. Should I use _screen.activeform?
>
>I'm not using the standard MM reporting options, so take this with a grain of salt. ;)
>
>Try defining the report variable as Private within the button.click. You might also (have to) lobotomize the report's private data session so it uses the same one as your form.
>
>Chris.