I need to implement a system that will stamp a users name and modification date and time based on one field changing. Currently, these stamps change when anything in a record changes.

TIA,

.sly

It is not clear how you are gathering the information now.

i.e Have you set this up in FileMaker, server, etc.

Lee

Edited October 8, 200718 yr by Guest

Sorry I didn't explain what I need very well.

We are running FileMaker Server 8

I have:

1. Field called "Modified By"

Options: Auto-Entered Modification: Account Name (Do not replace... Prohibit Modification...)

2. Field called "TSModified"

Options: Auto-Enter Modification: Timestamp (Date and Time) (Do not replace... Prohibit Modification...)

These apply to the entire record.

What I need is similar fields set up to auto-enter when a due date field is changed. I need to know when and who changes this one field.

Does that make more sense? I can post a file if need be.

Thanks!

The need seems very sensible. Howsever, how the fields are populated isn't because I'm still wondering if this is a Server enter feature or not.

Take a look at the examples for Field Modifiaction, or Audit, or Super Audit. The different ones I have seen can be limited to One Field.

I like the ones that are available at www.databasepros.com

Main Site >> Resources >> Search for [color:blue]Field Modification

there are several available, look for the version of FileMaker you are using, and read the accompaning notes.

or,

http://www.nightwing.com.au/FileMaker/demos.html

there are several available, look for the version of FileMaker you are using, and read the accompaning notes.

See if this helps.

WatchFieldModified.fp7.zip

I prefer the visual of using a trigger field as Michael has shown. It is very clear exactly what and why it happens. But, just to add an other option:

Case ( Textfield ; Get ( CurrentTimeStamp ) ; Get ( CurrentTimeStamp ) )

The idea is ... eiher way, the field is referenced; either way, the calculation will fire when that field's value changes. I think it beneficial to see both approaches because there are times that one method or the other might work the best. For instance, if you have several trigger fields but one result, the first method would be best. If you have one field but various results, the second might work better.

LaRetta