If you are not using the built-in 4D Backup System, then it will be near impossible to get a good backup of the 4D files. This is because the changes are made in memory and periodically flushed to disk (default interval of 20 seconds). There is no mechanism between 4D and time Machine to enforce consistency of the files during that backup, therefore the files restored from time machine will usually be corrupt or invalid.
The only way to properly backup a 4D Database is to use the built-in 4D Backup System. This will create a 4BK file every time the backup runs. In addition to that, you should enable the journal file. The journal file will contain all of the changes since the last backup. If you still want to use Time Machine then you should configure it to back up the 4BK file and the possibly even the Journal file. However, you mentioned the data file is listed as last modified 1 week ago; I would venture to guess that maybe you are looking at the wrong data file. You should probably double check the path to current data file in 4D to confirm you are even looking at the correct one, for example from the information page of the MSC: http://doc.4d.com/4Dv16R4/4D/16-R4/Information-page.300-3330288.en.html -Tim ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
