Coffee cups indicate the complexity of a file, tip or article. One coffee cup is the easiest and three is the most advanced.
To download a file, click on the green arrow icon next to the listing. If there are no coffee cups
or platform icons, the listing may be an article, Quick Tip, Knowledgebase or bonus file.
A long, long time ago in a far away land, Bob Cusick of Clickware sent me a log file that used a single field to log changes to fields. Through the years I modified it and released it many times but here’s the latest version. This version is so abstracted, all you need is a single custom function with parameters that specify the fields that trigger the log and the log field itself. That means you can copy and paste the formula from table to table and make minor changes to create logs in all your files.
This is a fairly simple technique using a two line script and the hide object feature to toggle the matching records option in find mode between Include and Omit. But, if you want to hide that nasty toolbar, this technique is critical in order to allow your users to do complex finds.
Demonstrates how to concatenate find criteria so that they can be restored by a user at a later time. This technique is superior to saving serial numbers as multi-keys, since it actually restores find criteria -- rather than the found set -- at that moment in time. This technique is completely dynamic -- new fields can be added without modifying the script.
The script in this solution applies payments to multiple customer invoices when under or over or underpayments occur. I've used this quite a bit in my own development work.
Many web sites indicate what fields are required with a red dot or an asterisk. Wouldn't it be nice to have the same feature in FileMaker but with very little overhead. Using Placeholder Text or Conditional Formatting, you can indicate required fields that are validated for empty.
This file is an old favorite of mine, since it demonstrates how to recreate the status area. I wanted to republish this for FileMaker 7 even though there are absolutely no changes to the FileMaker 6 version previously published. Basically, this file demonstrates how to create buttons and calculations to recreate the functionality of the status area, so you can hide it on startup and save all the wasted screen real estate.
This technique has changed so dramatically since I originally published it 10 years ago that it doesn't even look the same. The result is the same, but the way you get there is much easier to understand. In addition, the auto-enter feature is used, so there is no need to trick the user with multiple fields. Phone, Social Security Number (SSN) and Credit Card examples are filtered in this example.
The fastest and easiest way to locate overdue invoices, or any record using a date range based on the current date, is to use a script. I wrote this script years ago for FileMaker 3, and it has stayed the same until FileMaker 7. Though it hasn't changed that much, the formula has become more simple; and, you can now use Set Field instead of Insert Calculated Result.
This survey or questionnaire example file is designed to show proper relational design. It doesn’t have every bell and whistle. It supports a single questionnaire with multiple questions and multiple responses. I created this file because I see so many budding developers design surveys or questionnaires improperly and then can’t get the reports or statistics they desire.
Here are two calculations that calculate work days (days other than weekends). The first calculation determines the number of work days between two dates. The second formula adds work days onto a date.
Tip File
Tip File
