>You mentioned testing P-views.
>
>How do you test test them?
Just how you are: I generally develop my p-views by first developing the sql-statement (in the command window or temp prg if it's complicated). Then I add the where clause (just hardcoding a value). Finally I add the parameter (this is all in a prg or the command window). Once it's all working reliably, I CREATE VIEW AS to add it to the DBC (and immediately save the code version of the view in PRG, where I keep all view definitions).

>1. when the form pops up and prompts me for a paramter, I can type in the parameter I set in the WHERE statment (lnParenid, which is actually orders.norderid). If I do that, it will return all the values that match the parameter, correct?
That's the idea! :)

>My question is concerning the refresh statement Erik gave me, which reads:
>
>?orders.norderid = orders.norderid
>REQUERY(extended_price_detail)
>THISFORM.extended_price_detail.Refresh()

Well, you may need to experiment with this alittle bit. But where I would consider putting it is with the navigation buttons. If you "next" to a different order number, for example, you will want to requery the view and refresh the grid. So, Erik's suggestion (at least the REQUERY and REFRESH part) would work there.

May I make an additional suggestion? I find the book Effective Techniques for Application Development in Visual FoxPro 6.0 by Jim Booth and Steve Sawyer very helpful. I know I seem to recommend it almost exclusively: I don't mean to imply that there aren't other excellent books. But in terms of giving a clear and thorough explanation of the fundamentals (and not-so-fundamentals) of development...well, it really helps me alot.

That's not to say you shouldn't keep posting here, and I don't know what book you are using, but if you're looking for another one...:)

Good luck.