Good thought, but it still is not working. By that I mean that the column displays the same client name in each row, despite the fact that for each row in the controlling table, CUSTNO (the field on which the relation is built) is different. I have checked the index and it seems fine. I have set the same relation in the dev. environment and browsed the tables and the relation seems to work fine. I will have to now check it at runtime to see if it is somehow getting screwed up at that point (I already checked to make sure it exists via the Data Session window, but did not check in more detail, yet).

>What is not working? In some cases you must change the value of Sparse,
>
>>Well, yeah, I know - thought that was obvious, but I guess I should have stated it - I see that I didn't make that clear in my posting. But it's not working. The relation is set, the ControlSource is set, but it's not working.
>>
>>>

Yourgrid.yourcolumn.ControlSource='yoursecondtable.yourfield'

>>>
>>>>I don't find myself doing this much since I'm using the contents of a SQL statement so often, however I need to have one column of a grid display a field from a related table. I have the SET RELATION set up properly, of course, and this seemed to work fine a week or so ago, but now I come back to the form that contains the grid to try to finish it - it got put on the back burner for awhile - and now it's not working. Is there a trick to this?
>>>>
>>>>Russell Campbell