>Terry:
> I agree that, in a One-to-Many Relation, the Child table should be the "Many". In your example, it would be the Address table. If I reverse the Relation, then I would need a Filter (or keep it Indexed and constantly use WHILE) to isolate one county or state. If I were only interested in New York, for example, I would still get every Child record unless I Filtered or used WHILE).
> I think that my problem is caused by a FoxPro bug, and I developed a workaround by using SEEKs and SCAN FORs. So far, so good. After knocking my brains out (and those of everyone here) all week, I am ready to celebrate.
>
>Jerry

Last word on this Jerr'

To my mind, if you have a set relation going between the main table and the look-ups, then as you move the file pointer in the main, then the approp. rec in the look-up should be fetched. I don't know where filters would come up in it.
But maybe we're talking at cross purposes and I haven't understood your situation. I'd agree that your look-ups would be better indexed on the key by which they're ref'd by the main table.

Terry