Just to check that I understand @Dblookup-caching

I just want to clarify a thing regarding @DbLookup and caching of data:

I have form that performs quite a lot of @DbLookups. They all currently have @DbLookup(“”:“NoCache”…) specified.

My intentions is to remove the “NoCache” when it isn’t necessary to (somewhat) improve performance of the form, but my question is: When is the data cached and re-cached?

As I understand - the first cache is made when the @DbLookup is performed the first time (just as it would do with “NoCache” - duh). But if the underlying data is changed - when will the @DbLookup discard the cache and make a new cache? When the CLIENT is closed and reopened or when the DATABASE is closed and reopened?

Is the cache stored in memory or in a file (like desktop6.ndk)? Or both?

Subject: When the client is closed and reopened, but there are other options

Read this excellent reveiw by Andre Guirard: @Dbfunction caching strategies

Subject: Thank You! I had already eyed through that article, but not read it in detail - got to do it now…! :slight_smile:

Thank You!Now I can form a plan for redesigning the hidious form with huge amount of @DbLookups