I agree 100% with Erik (how could I not?), but I will tell you what may be going wrong with the one to many.

If you are letting your relationship in the DE manage your child grid, then you need to set the property onetomany for the relation to .T. If you are using link master in the grid (not something I've done a lot of), then I *believe* you do not want to set the 1-many in the DE at all.

>I have a many to many relationship established, using an intermedaite table to link index values from both tables.
>
>I used to handle the display of a grid of related records in my forms by using a view, and requerying the view whenever changing records.
>
>I was hoping I could eliminate the added overhead of querying the view by just creating a one-many relationship in my data environment (either between the parent and intermediate table, or for both relations) - but when I try this, I still see only one child record for each parent!
>
>I don't know if I'm doing something wrong, or if the intermedaite table is creating a level of complexity which doesn't allow the desired result. I could go back to the views (or sql into cursor), refreshed for each record - but if I'm missing something that would make my life easier and my application faster, I'd like to learn about it!
>
>TIA
>
>Happy NewYear!