>>I cannot open view1 with data since I don't know which data the user wishes to use in the report. When I know which data it is, it can be multiple values. Since I know of no way to create a multi-valued view parameter (which is usually the integer primary key value ) I populated view1 from the multi-select list prior to requerying view2, which didn't work.
>
>Hi Gil,
>
>I have a feeling you can accomplish what you want using an updateable cursor instead of view1 to hold ONLY the primary keys of the records you want to fetch through view2 and then for view2 use:
>
>select yadayadayada FROM mytables_and_joins WHERE primaryKey IN (select * from my_cursor)
>

Alex,
I did, in fact, end up using the updateable cursor, which does work. It's not as clean as I'd like it but it'll do for now. I'm going to look at Paul's suggestion as well.
I do find it curious that view1 must be loaded from the underlying data.


Thanks again,