John,

I'm in code avoidance mode *g* I don't do anything there that I don't have to. All my p-views use the ?ParentTable.iID as the parameter. It's a little more flexible for me because the views aren't bound to a form that way. I've also used simple memvar references but I've been happier with using the ParentTable itself, it kind of also "documents" the parent-child relationship the view represents. My child forms open in default-datasession because they launch from a private-ds parent form.

>A side note that may be relevant: I always create and modify my views through code for the reason that the View Designer doesn't like parameterized views (THISFORM can only be accessed in a Method error). I write the code into a PRg, run it...if it works, I add it to a MAKEVIEWS.PRG program that has the code to generate all of the applications views.