I'll jump in (since you copy me on the msg to Erik :)

>I apologize for asking so many questions about this one topic, but if I don't ask questions, my chances of completing this form successfully are slim!
No problem. Parameterized views aren't simple to grasp--though it'll seem like that once you *get* it!


After I completed the SQL statement and "browsed" the view, a form popped up that asked me for a parameter, and didn't show me the records in my orders detail table as it had before.
That's right. A form will pop up when the parameter (lnParentId) doesn't exist. When I test p-views in the command window, I first set lnParentId equal to a valid value, then issue the SQL statement. Or, you can just put the value in. This is one of the nice things about p-views--you don't get an error just because the variable isn't defined.

>So, I went in and changed the SQL statement for my view to:
>WHERE ordersdetail.norderid = ?orders.norderid
This looks right. You can use the literal field (orders.norderID) or some people prefer to set a memory variable equal to the field value first. My personal preference is the former--my fields don't tend to change, and I hate haveing to remember which memory variable I've used :).

>It said to throw a variable into the selection criterion, so that it read, ?m.Cust_id (at least that is what it used in the example).
You understand that the "m." just means that you are explicity refering to a memory variable--not a field, right?

HTH