>>
>>Thanks Jess
>>Your suggestion got me to the problem. The relation does not change but the form I use to define the filter uses combo boxes to display choices. One of these boxes displayes information from the file that the grid is related to. When I list this file it messes up the relation back at the grid. I found it by creating a test button that just puts a manual filter on the grid. This worked fine - so the problem had to be the filter form - and therefore the combo box. I will try a private data session for the filter form to fix it.
>>
>>Thanks again
>>
>>Terry
>
>Terry - sorry for jumping in here but I had a similar problem. I was looking up inventory records in a grid using a combo box and had the same sort of thing happen. I removed the relationship in the forms data environment ONLY(ie - not in the DBC) and it worked fine.

Yah appearantly foxpro grids are more sensitive to outside sources than forms for example. I routinely open more than one copy of a table (ie Misc_Info) using different indexes and aliases to populate combo boxes. This process never seems to affect relationships involving that table. Each "again" seems to run independantly. Obviously not grids though. My gut feel is that this is a good target for MS to look at say in Ver 6? - along with the report writer.

Terry