You've probably already opened a shortcut link in a text browser and realized it does not actually save the find info, rather a list of all the RecordIDs (filemaker schema ID) of the records in the found set you were looking at. Thus you can't scrape the find data out of one of these files.
Saved finds are a quirky thing in FileMaker, you have no scriptable control of it, and the saved finds are based specifically on the user, not the session or the file. To share the saved finds natively, it requires logging in to the same user account. But that's not helpful at all is it...
Theoretically, a "find transactions" log could potentially be scripted using a combination of design functions and script steps and a trigger.
Basically your OnModeExit trigger would assemble some sort of log of your current layout and find request, then save it to a transactions table.
Something like this to assemble your request:
//Check for find mode
If [ get(windowmode) <> 1 ]
Set Variable [ $layout ; get the layout ID ]
Set Variable [ $fieldlist ; list of field objects on layout ]
Go To Record/Request [ first ]
Set Variable [$i ; 1
Set Variable [ $ii ; $ii + 1 ]
Set Variable [ $requests[ $1 ] ; List ( $requests[ $1 ] ; GetLayoutObjectAttribute(GetValue($fieldlist;$ii);"content") ) ]
Exit Loop If [ $ii = ValueCount($fieldlist) ]
Exit Loop if [ $i = # of requests ]
You would have to store that, then reverse it to rebuild the request. You would also need to come up with ways to handle omit.
Huge pain, but theoretically possible.
Thanks Mike – I appreciate your thoughts. Would be GREAT if there was something like the snapshot, but a saved find. I’ll investigate further.
NightWing released a demo file using FileMaker Pro 9 called Find Log System.
Pretty sure Matt Petrowsky released a video tutorial years ago demonstrating how to save find requests and field criteria but I cannot locate the tutorial.
Hope these helps.
FileMaker's knowledgeBase on Saved Finds notes that:
"Note The saved find is also available to any network clients that share the account."
If you were to build a separate "Find Interface" file which opened only with a default account and set it up for performing and saving finds, all users would have access to the common-account's Saved Finds while in that interface.
This could be tricky, as you probably don't want anyone editing records with a shared account. One could script capturing record IDs from the found set and restoring the same record set from that info back in the file where they each have separate accounts.
On the other hand, if the Find Interface file were done up as a Reporting module without direct editing capabilities, both saved finds and reporting based on find results could be run using the common account without risking the integrity of tracking data edits.