Well the title says it all. I've inserted an auto-enter timestamp but would like it to update whenever a field is typed in, not just a new record is created. Is this possible?
Then all you need is to set up the field to auto-enter the modification timestamp.
If memory serves the modify is noted only for keyboard entry and only after a commit.
This is not the case. Any modifications of the record, via the user interface should cause the field to update. Importing would too if you enabled auto-enter as part of the import.
Instead of changing your existing field which is set to Creation Time Stamp ( which you may later wish to be able sort your records by), add a new field to your table called ModificationTimeStamp and have is set to be a Modification Timestamp.
It is already a modification timestamp. What am I doing wrong??
Plz show screenshots of field definition like above
This looks perfectly fine for me. The value of this timestamp does not change if you change any other field of this record?
I believe that modification timestamp is at the record level not for a particular field. So, possibly until you go to another record, it may not update that Timestamp.
Depending what you need, you could set a script trigger that would do a SET FIELD and update a regular Timestamp field with the current date and time.
This seems like it would make sense. But I am unsure how to set up that script trigger.
I've even tried writing a start-up script to insert the current time and date and still nothing...
The following date field with an auto-enter calculation will update to enter today's date any time that Field A is modified:
Let ( F = Field A ;
Get ( CurrentDate )
Be sure to clear the "Do not replace..." check box
Are you able to modify any value of this database at all, or is this all 'read only'?
Yeah I'm really not understanding. I'm on Filemaker 13, on a Mac if that helps?
When I right click the field to "set trigger", It asks me to pick the trigger, which all involves interacting with the field in some way which is not what I want.
So then I go into "File>Manage>Scripts" and am a bit unsure as to how to proceed. You guys are exceedingly patient with me so thank you!!
Not read only! I created it from ground up (surprising, I know) yesterday. Learning the program as I went. It's the coding stuff that is really confusing to me still.
My suggestion does not use a script trigger. It's a field option specified through Manage |Database.
The 'Modify' timestamp field will change when any field in the record is modified by a user changing data in a field and committing the record. It doesn't change until the record is committed. Record locking is the only method to determine if information is being changed our could be changed.
It is not a historical record as it only shows the timestamp for the last modify/commit and therefore isn't an audit trail. There could have been any number of previous changes by any number of users.
I'd have to test to see how this works with scripted changes but you could do that.
1) Do you want a timestamp for when ANY field in a record is modified and committed
2) When a specific field(s) is modified and committed
3) Do you want an audit trail or just to know when record was last modified.
1) Yes. Any field in a record is modified.
3) No audit trail! Just when the last one was modified.
You are all very helpful and amazing!
I was apparently not committing properly (insert joke here). It is working now!
Experienced FM users click somewhere outside fields after editing. This forces a commit.
"Experienced FM users click somewhere outside fields after editing. This forces a commit."
The old masters press the Enter Key on Windows and I think its the Enter key on macs...
Sometimes the old masters in order to prevent the click/commit place an invisible button over the layout or uncheck the box in the layout designer. If that checkbox is unchecked then a dialog will appear asking to save.
Retrieving data ...