Chris,

>>>However, I think I didn't ask the question I wanted to. I guess I should have asked how to have parameters were sometimes optional. EG: So the same form or report works whether it's for selected customers or all of them.

>>Ah. Well, I will included a parameter in a form Init() that is the ID of, say, the customer I want to have come up on the Customers form. So, you could check if the parameter has been passed--VARTYPE(tnID)="N"--and if it is then change your DataEnvironment to use the lv_Customer view, and if it's not set the DE to use the lv_Customers view. (Just for example).
>
>The forms in question are asking the user for the value, not receiving it as a passed parameter. Verifying passed parameters is pretty easy, but the forms aren't receiving it, they're asking the users for it before requerying the view. I really want to avoid that kind of conditional logic if I can.
>
>With "SELECT * FROM customer WHERE customer.lastname = ?vp_lastname", it's easy enough to pass "" as the parameter and get all customers, but what about a date(customer.lastdate) or integer(customer.custid)?

You could have either a compound WHERE, or you could have a different view for each type of query. CustomersByLastName, ByDate, ByCustID, etc.

>>I also noticed you had another question in your original post about view parameters based on a field in another cursor:
>
>Then this will be a no brainer once I get the first half right. Cool.