Wow, didn't know a chestnut that old was still in there.
Today, use a timstamp field that auto-enters the modification timestamp.
And you can then sort on that field to find the records with the most recent timestamp or perform a find in this field to pull up records in a particular range of values or that are greater than a specified value.
Yes, I am ware of that. But where do the wrong results come from? I know there is an easier/more elegant method, but I have to update all databases. So, my question still is: is the method in the link correct (as in: does it function as it is suppost to)?
(My question is NOT: what methods are there to accomplish the task?)
Why waste time with an option set up for FlieMaker 5.5?
Why not use one that works and is far simpler to implement?
(No offense, but I don't choose to spend the time analyzing the details of that very out dated method in the KB article, a quick skim was enought to tell me that it's not a good option for today's systems.)