>Hello Jim,
>
>But it is a one to many relationship. I was pretty sure that I had forgotten to set the linkmaster relationship. I was sure that was the answer. Not! But I remembered John's comment regarding deleting the relationship in the Forms DE. That apparently works. I still see the multiple task orders in the Task Tab and don't have the navegational problems in the detail form or the '*' in the browse tab. Which is all correct.
>
>But this is very disconcerting because on page 290 of the VFP Developers Guide the set up for one to many is described both ways: using the forms DE and using the forms properties. It dosen't state 'use one or the other - not both'.
>
>I actually have two pagesframes that use this method: The Patient form with the many open Task Orders for each Patient and another pageframe with Employees and a tab showing the many Task Orders that a given employee can be assigned to. They both seem to work now that I deleted the relationship in the Forms DE.
>
>I appreciate your response very much. Any further suggestions will also be appreciated. TIA.
>
>Regards,
>
>Paige

****************************

Paige,

As an alternative to a relationship, you can do what you're after with SQL. Using a relationship has the advantage of being easier to implement. The downside is that if something happens to your indexes, or your ordering you have a problem. There is also the issue that with a relation, your app is much more difficult to scale to a client server environment. This may or may not ever become an issue. However, with SQL, you can get extremely reliable performance in a file share environment, and easily scale up to client server.

The details get a little involuted, but if you are interested, I'll be happy to provide what information I can.

Regards,

Jason