# Best way to clear cache of detail (child) table

**URL:** https://talk.remobjects.com/t/best-way-to-clear-cache-of-detail-child-table/34353
**Category:** Data Abstract
**Tags:** delphi
**Created:** [November 18, 2026, 12:55pm UTC](https://talk.remobjects.com/t/best-way-to-clear-cache-of-detail-child-table/34353 "2026-11-18T12:55:24Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![fvancrae](https://talk.remobjects.com/letter_avatar_proxy/v4/letter/f/ad7895/32.png) [@fvancrae](https://talk.remobjects.com/u/fvancrae)
#### Post date: [November 18, 2026, 12:55pm UTC](https://talk.remobjects.com/t/best-way-to-clear-cache-of-detail-child-table/34353/1 "2026-11-18T12:55:24Z")

</div>

I would like to check what the best way is to clear the datable cache of a detail table.

I have several TDADataTable classes that are linked via master-detail link.

I have a grandparent table G, a parent table P and a child table C.

At some point I loop over P and change the database table C via a method other than the child table C object.

After the operation I want to clear the cache of the C records.

What is the best approach to do this?

1. Call G.P.C.Refresh(); a single time (for a datatable cursor pointing to an arbitrary P record)
2. Call G.P.C.Close(); followed by G.P.C.Open(); a single time (for a datatable cursor pointing to an arbitrary P record)
3. Call C.Refresh(); or C.Close();C.Open(); for each P record that was impacted?
4. Other solution?

Note: Claude suggested option 1 and said the Refresh() option might work

 ![image](https://talk.remobjects.com/uploads/default/original/3X/8/c/8c87954af022f677b992088d43b10ca4c549b420.png)

---

<div class="post-metadata">

### Author: ![EvgenyK](https://talk.remobjects.com/user_avatar/talk.remobjects.com/evgenyk/32/16_2.png) [@EvgenyK](https://talk.remobjects.com/u/EvgenyK)
#### Post date: [November 18, 2026, 2:58pm UTC](https://talk.remobjects.com/t/best-way-to-clear-cache-of-detail-child-table/34353/2 "2026-11-18T14:58:34Z")

</div>

Hi,

Claude’s recommendation is correct - table.Refresh is enough.
