Kevin,

PMFJI, but as to your original question, is this a parent child relationship? If so, then to refresh the child record you will need to move the record pointer in the parent table/view.

HTHs,

>>>>So why not a view?
>>>
>>>Certain users have the ability to change data in the tables directly in the grid. I was told that views would be complicated for this because you are not actually changing the values in the table and have to make function calls to update the table itself.
>>
>>No - views are not complicated and, as I understand you, are ideal for this.
>>
>>So, in the View designer, on the "Update Criteria" tab, you check "Send SQL Updates" and check, under the pencil column, all the fields that you want to allow the user to be able to change.
>>
>>Thus your view becomes like an updatable single table.
>>
>>HTH
>>
>>Terry
>
>OK, so I created a view. One table is tiny, but the other is rather large as most of our tables are. When I browse the created view, it runs a query for about a minute or so then pops up. Is that what would happen if I used the view in a form? would it really take all that time to query each one? If so, that is way to slow and inefficient for us to use that method with our large tables.