>I've created (2) parameterized views using one parameter for a many to one relationship. This works great. My question is about the parameter itself. Should it be a public variable? I would like to use a property because if I update the view and somehow the variable loses scope, my requery results would be effected. Can the view have ?oObj.key as a parameter and is this an "accepted" practice? It would be nice if you could pass parameters directly to the view but I don't see this option as available.
>
>TIA

The variable can be declared as PRIVATE in the method or procedure which is going to requery the view.

Steve