Crystal Report "set to null" by each parameter???

It sounds like you are by-passing the LBI parameter screen which uses the Business Objects parameter screen. The BOBJ parameter screen is much more robust in functionality but far more confusing for the end users. What Lawson has done with Reporting Services is use the BOBJ API to create their own parameter screen and this is essentially what youd have to do to get rid of this option (i believe, other more advanced BOBJ users, please chime in).

But to answer the initial question, it passes a "null" value to the parameter. If the parameter is required to have a value you cant submit unless every parameter has some type of value.

hth
matt

Yes, we are removing the LBI parameters (seems like the presentation was better or functionality--I honestly don't remember why). And I do use stored procedures, particularly for this one report, as a data source. I understand this Set to Null appears when using stored procedures.

I don't want NULLs passed and I'd like to remove it from the screen. Users and internal people go "What is that Set to Null" thing and I just want it to go away.

I've looked at the BO site but the solutions seem needlessly complicated JUST to remove this. Seems like it ought to be part of each parameter's setup as an option.

From Business Objects' website. I've never used a Command, but when I tried to test it, and this report has 8 or 9 parameters, I'm getting errors, most likely syntax. But you set up the Exec call to the sp, presumably with parms in (), and then you have to set up each parameter individually (but only part of the set-up, not everything I use, so will that be available if I was ever successful). Here's the kicker: after you do all of that, if you have a syntax error, you're not sure what's wrong and you have to set up each parameter again. AGHHH. Again, possibly oversimplifying, seems like it should be a checkbox on the parm set-up.

1. Create a New Connection; Insert a command instead of using a stored procedure.

2. In the Add a Command, Write

Exec StoredProcedureName{?Parameter}

3. {? Parameter} is created at command level i.e.

Parameter List-->Create-->Give the parameter name-->Type of the parameter-->OK

Note: Type of the parameter should be same as in stored procedure.

4. When you refresh the report Set to Null option has been removed.