Hi, I am new to the forums and have a concern with FMP 7. I have been learning to use it for a project at work for the last month now and so far love it. However, I have noticed something that appears to be a major bug in my FM. In the memory settings, I changed the "Save cache contents" from the default "during idle time" to every 10 minutes. I have found that neither of which are actually doing so. I had FMP running for 3 days straight and added and modified records during that period, and never once did it save the cache. I know this because in the properties of the DB file, the last modified date and time were the last time I had closed the file (3 days prior). I found however that if you use the "Flush cache to disk" script, it does it like it is supposed to. I called Filemaker tech support today to question them about it. The person that I spoke to opened up a sample DB, set the save to every 10 min, modified some records, and then we waited 15 min. He was a little surprised to see that for him, it too never saved the cache. This can be a huge problem, as the cache sits in RAM, and if someone has entered a lot of data into FM, it would all be lost if power were to be lost or any kind of lock-up occurs resulting in a hard reset. Maybe I am totally off-base here, but please take a close look at your databases and see if the same problem is happening. Thanks, Sam

Have you tested it by force quitting or unplugging your computer to see if it actually did save the changes?

No, but I am going to right now, I just modified some records and am now waiting for at least 10 min and will just pull the plug and see what happens.

Ok, now I am confused. I just pulled the plug on the computer running FM, restarted, and somehow, the new records that I added were there. However, the file still states that the last time the file was modified was a few days ago. Is it possible that FM is updating the file without it being marked as such? And if so, why does the flush cache script function cause the date modified to change?