>>It's SO annoying, because this code definitely worked in the CR preview window before, and works OK if I manually step through the code in the debugger. I just upgraded to 8.5 today and I really had hoped the problem would "magically" go away. No such luck...
>
>Paul,
>
>What exactly are you using the parameter fields for? I honestly don't know if this is the problem..BUT.. in my report design if I don't have intentions of prompting the user for any values, then I just stick to using regular formula fields and populate those at runtime with whatever values I need and save the parameter fields for when I only specifically need user input.
>
>Just a thought..
>
>Laterness,
>Jon


Right now, not much. I've taken the approach of passing variables in my temporary cursor. But, I'm in the process of developing a generic report framework for my apps and I can see some value of being able to pass a variable directly. Since it's possible that these reports may end up on the web, I thought it would be kind of cool to be able to let CR prompt the users for these values if my app didn't provide them. I don't have any "scenario" where I'd need this right now, but it seemed kind of interesting. I guess I made the assumption that parameter fields were meant for passing parameters ;-) I might try using the formula fields if I can't make this work. Thanks for the idea.