If you "un-sort" records in Filemaker, they will default to the order in which they were created in, but I don't know of a way to find out a timestamp for when those records were created. You can't, for example, pull that stuff out of DDR, as far as I know.
You could of course create the Date Of Creation field, and populate all the existing records with a set date, so that they're not empty going forward, but that might not be of much help.
If there are other records (linked to the records with the forgotten creation date/timestamp),maybe you can deduce the missing creation dates from there, assuming that those records do have a creation and/or modification timestamp. Using these dates as reference points you might be able to interpolate creation dates for any other records in between, working from the unsorted/creation order of your records ...
Missing dates might also be recovered from other sources outside the database (table), like emails, paperwork etc ...
If you have daily backup, you can get the date from them.
The horse has bolted, I'm afraid; that is not something FM stores away. Similar to James's idea, I suggest you create a text field into which you store some record data such as: "This record was created between xx/xx/xxxx and yy/yy/yyyy. FM recordID: " & Get ( RecordID ). To populate all existing records, use Replace Field Contents and this calc. Once that is done, set up a calc to capture whatever data you'd like to record as future records are created. You can use a calc to capture much more than just the Timestamp, for example:
"User: " & Get ( AccountName ) & " – at IP address: " & Get ( SystemIPAddress ) & "¶" &
"NIC address—" & "¶" &
Get ( SystemNICAddress ) & "¶" &
"Host: " & Get ( HostName ) & " – " & Get ( HostIPAddress ) & "(host)" & "¶" &
"Device: " & Get ( Device ) & " – at ID: " & Get ( PersistentID )
"Time: " & Get ( CurrentTimestamp )
Many thanks to all you guys for yours advices.
Yes, Keywords, i will use your calc in the future. You light me having a timestamp is not enough. But to know also who and where has create or change a record, is important.
Thank you again.
Another added thought: Create a log table or file where all such data is stored for each created, modified and deleted record. It could even be used to save user entered data and would then allow to roll back a database to the date of the last backup. I do this actually using a separate utf8 encoded text only file where I append such data. You could use eSQL getting all into a structered text field which is storing away and does not require thinking too much.
Many thanks, that's a great idea !
It's sound good and I'll try to do this.
Hope to be on capacity to do it !