Thank you for your post.
As documented on page 37 of FileMaker Pro 13 Help, "Snapshot links cannot be converted. You must convert the database from which the records were found and then re-create the snapshot link."
Just a suggestion:
When converting files, we don't suddenly remember to consult Page 37 of the FIleMaker Help. Seems to me it would be a good idea to present a quick reminder of whatever might require post-conversion attention, just like other dialog boxes that appear when a process is done. Even if the reminder does nothing more than say "refer to Page 37" it would still be better than nothing. No message or dialog creates the false impression that the conversion was successful and the only errors appear in the log.
Maybe I misunderstood the original post, but my understanding was that Dennis Burnham was talking about the "Save Records as Snapshot Link" script step where the path specified could be corrected during conversion (like external file references to .fp7 files do not keep the .fp7 file extension, it is removed upon conversion so the external file refs keep working). Dennis did not mention explicitly the script step, but his original post mentions re-writing the script in both the description and workaround.
What confuses me, is that if I create a .fp7 file with a script that contains a "Save Records as Snapshot Link" script step where a file path is provided, and then convert the file, the new filepath shows .fmpsl at the end (I tried performing the conversion both with 12.0v5 and 13.0v3 on my mac). I don't think the original post is concerned by the snapshot link files that were generated before the conversion happens, but if I am mistaken, please let me know.
Yes, in the original post I was describing a script step that had been written in FMP-11 to create a snapshot link. When I look at that script in FMP-13 the extension is unchanged.
FMI tells me that it's not something that gets converted automatically, and my response was, OK, but shouldn't the users be informed at the end of the conversion to alert them to any possible (known) detail that is not handled by file conversion -- instead of going to the Help file to go searching.
In your conversion, fpsl got converted to fmpsl . In my database it did not. Make me jealous!
Hi Dennis, I'm sorry if the fact that I'm observing different results on my own workstation infuriates you (part of me would have preferred witnessing the same behaviour). Can you give more details about what FM Version you are using for the conversion and what OS your workstation runs? If you start with a blank .FP7 file, create a script that has the one script step with a file path specified, do you still obtain .fpsl as an extension instead of .fmpsl?
I am wondering if a common cause of this issue could be when the filename is defined on a variable and then, only the variable is referred by the script step.
Obviously, the script conversion will not update the variable formula as it can do on the save script step.
But as far i know, on the exact same case, with the save steps when the extension is fp7, it is updated "on the fly", during execution.