I'm trying to set up a check box and timestamp feature to the database so we know when things moved from graphics into production or in production to shipping, like that. What I'm trying to do is when one of the checkboxes is clicked it updates a timestamp for that specific job (Going from graphis to production). I've tried a few things and I can't seem to get it, all my timestamps update together. I know I'm missing a step in here to seperate them but keep them on one page.

Help?

I would suggest making the checkbox field a button instead. Then, you can create a script using Set Field that will place the Get(CurrentDate) function into your date field.

I know I'm a novice, so forgive me when I ask this:

How do I go about doing this?

I think you are going to be best served by learning more about scripting and calculations. If I try to teach you something out of context, it will never make sense. There are lots of resources available so I will refer you to several I believe will help you:

Professional Foundation Training Book and CD

http://www.filemaker.com/developers/professionaltraining/bookcd.html

My Video Training Bundle:

http://www.databasepros.com/videos.html

How about this example file of checkboxes, scripts, and time stamps?

Simple enough and hopefully clear enough about how to manage this process.

You are welcome, Samantha.

TestCheckBoxDated.fp7.zip

Edited October 4, 200619 yr by Guest

Hi Samantha

give a try to this.

( No script needed )

_8_CheckBox_TimeStamp.zip

That's a good solution to trap single values. I'll have to use that in the future.

The advantage to the script method is more obvious in a production setting (my field of expertise).

Let me explain:

The job is partly completed and we have a time stamp on step one.

We complete step two and time stamp that step.

We need to keep the first time stamp, but checkbox step two for status display.

Uh'oh, we made a mistake and need to re-do step one. So we checkbox 1 again, changing the status, updating the timestamp in checkbox 1, and leaving the previous timestamp in box2.

All of this allows us the ability to track workflow.

I might add that the repeating field I used for the variables also has the advantage of 'grouping' the results. Some people want seperate fields for all variables and that's Ok too I just used a repeating field for simplicity.

The reason not to use a checkbox field is the ability to affect other fields within a script.

What do you think?

I'm sure there are lots of ways this can be accomplished.

Oh excellent! Thank you so much!

You're welcome, Samantha.

Some of the ideas presented in my example are gleaned from others here, some from experience.

Glad to be of assistance.