From Comment's post waaaay back in 2007:

 

Posted March 1, 2007 (edited)

I don't know why you bother with the times - Filemaker will do it for you*. Just enter the search criteria as a date range:

YourTable::YourStartDate & ".." & YourTable::YourEndDate

BTW, it's preferable to use Set Field[] instead of Insert Calculated Result. [my formatting]

-------------------------

Why is Set Field [] preferred? 

28 minutes ago, WF7A said:

Why is Set Field [] preferred? 

Because Insert Calculated Result[] requires the target field to be present on the current layout, while Set Field[] works entirely at the data level. Therefore Insert Calculated Result[] is more suitable in situations where the script's purpose is to assist the user in data entry. In a situation like the one described in the linked thread, where user entry is (no longer) required, it is better to bypass the layout level and avoid the risk of breaking the script if the field is removed from the layout.

 

Edited April 5, 20223 yr by comment

Ah! Thanks!

However insert calculated result to a variable is still an option and can be performant for some operations

https://community.claris.com/en/s/question/0D50H00006dsly8SAA/use-insert-calculated-result-to-concatenate-strings-groundbreaking-performance-leap

10 hours ago, Ocean West said:

insert calculated result to a variable is still an option

I don't know if "still" is the right word to use here, since it is a relatively new option. I don't think it even existed back then.

But yes, if you use a variable as the target, then of course you're working at the data level. And then the comparison is to Set Variable[], not to Set Field[] as above. And if you also select the Select entire contents option, then those two are identical (at least conceptually, if not performance-wise).