Al,

I'm at a loss then. Even where I have used SET RELATION, I never used LinkMaster.

Eventually you might want give parameterized views a try. The technique is well-suited to this situation.

*** just for an example

CREATE VIEW lvw_ItemsByOrder AS SELECT * FROM items WHERE item.fk = ?thisform.OrderPK ORDER BY items.item_number

Then in your form you can add the local view to your DE, set noDataOnLoad to true. When you refresh (change) the order record, you can REQUERY the item view. In my example I show thisform.orderPK...you can add a property to your form and keep it synchronized with the currently displayed order--use this as your view's parameter.

I hope this helps...I've been working on transitioning to views and so this is coming from a p-view newbie! For example, some folks might create a view that includes the order table. While I defer to their greater experience, I found this way of easing into it worked better for me.

>Thanks for the reply. Yes, link master. Typical order / item parent child. Order.pk_order relates to item.fk_order. Related in the DBC. Related in the form's data environment. The grid has other columns. For example, items has a product number that relates into a table of descriptions.
>
>I always did this before VFP with the order on top and an item browse on bottom half of the form, etc.
>
>I havn't ventured into views yet.