>>I have a top-level form with three pages on it that is the main form for my app. My DBC has persistent relationships between 4 tables. I dropped these into the data environment for the form and the relationships are there. Sometimes however the relationships quit working. Example: I have a grid on the first page that is the parent to the first grid on the second page which is the parent to the next grid on the second page. For some reason the second page is always the child records for the first record in the grid on the first page, even if another row is selected.
>
>This is due to the fact that a THISFORM.Refresh() only refreshes the active page in a pageframe. To make sure that all pages show current information when they are shown, put a THIS.Refresh() in the Page.Activate event.
>
>>Also, something causes all the relationships to quit working every once in awhile even though I can check the data session window and all the relationships are still in place. Is there a better way to do this? Maybe create the relationships in code instead of using the data environment. Thanks for the suggestions.
>
>
>I can't explain what causes this, except to say that it happens sometimes, and is one of the reasons I don't use relationships at all (parameterized views instead). Sometime the cursors "forget" their relationships. All you need to do to remind them is to move the record pointer. GO RECNO() usually does the trick.

I found at least part of my problem, I was trying to do a COUNT FOR and it was moving my record pointers around. I am going to try a SQL instead. Is there any good FAQ's or white papers on using parameterized views? I have read a lot of messages about it but I have never used it myself. I have trouble getting views to work, I get everything just the way I want and then when I try to save it in the designer I get some error about can't find a specific field that I know exists. Thanks for the help.

Shane