>>>>I want to ...
>>>>
>>>>- build a cursor containing a subset of the main table...
>>>>- populate a grid from the cursor...
>>>>- have the user make a change via a pop-up edit window...
>>>>- save the change to the original main table...
>>>>- have the grid (cursor) also reflect the change
>>>>
>>>>
>>>>I'm sure that this is an 'every day' kind of thing, but there are so many ways to accomplish this... I'm looking for suggestions...
>>>>
>>>>Thanks
>>>
>>>You should have generic method which will get table records into cursor (SELECT or SEEK/SCAN) and use this cursor as grid.recordsource, actually nothing more. It's important that cursor will carry all primary key fields from the table.
>>
>>That's what I'm doing but I must not be doing it right...
>>
>>The cursor is the recordsource for the grid... when I pop-up the edit window, I'm displaying the record from the *main table*, not from the cursor. I did this because I'm not sure how to get changes from the cursor back to the main table...
>>
>>THanks
>
>If cursor holds primary key field(s), then you can always SEEK in table too.

But I'm updating the main table already ( it's displayed in the edit window ) so I'd locate the record in the cursor and update is as well?

Thanks