This free example demonstrates how to create an extremely flexible audit system to log field changes in your records. The bulk of the work is done through Custom Functions. Once the custom functions are set up, you can add logging to a table easily by creating two or three fields in your table and a layout with the fields that you would like to log. You can track any type of field including repeating fields and container fields.

Features include:

• Uses custom functions to do 99% of the work
• Ability to log repeating fields
• Ability to log container field changes
• Fields can be created in any order
• Log is triggered via a modified timestamp field
• Ability to log related fields or not
• Uses a user defined layout to add/remove fields from logging
• Uses text formatting to aid in readability
• Adds a date banner to the log between different days
• Custom functions include comments
• Includes a white paper explaining how to recreate the example in your own solution
• It's free. ;-)

The example solution can be found in the "Tips" section of the CNS website.

In part I of the drag and drop test we looked at having a field you can drop to, "active text", but still have the ability to type in the field. This effect is desirable if you want users to be able to drag ID keys to a field, but also be able to type them in as normal.

So what if we do not want the user to be able to type into the field? What if we only want the "active text" field to be a drop zone? That is where "Part II" comes in. If you have not already read Part I, you might want to read it first because it explains things more thoroughly.

Read full article...

Drag and Drop in Filemaker? With FileMaker Pro 7, many new things are possible, including dragging data around your layouts. (Example database and details included in full article)

Read full article...