>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

Tom,

I have always doen it this way, whenever the requery is to be issued I create and populate the parameter as a LOCAL.

LOCAL lcViewParm
lcViewParm = Obj.Property
Requery("TheView")

This way there are no public vars floating around to get clobbered, the view is not bound to an object so it can be used independantly of the object's name, the code that requeries the view has the line that populates the parameter right before it so it is self documenting, the view can be used and tested outside of the application (no object dependency).