All the more reason not to name files explicitly if you can possibly avoid doing so.
valueListItems ( "YourFile.FP7" ; "valueListNameInQuotes" )
will fail with the upgrade.
ValueListItemes ( get ( filename ) ; "valueListNameInQuotes" )
Will not fail with the upgrade.
RightWords ( Get(FilePath ) ; 1) returns the file extension, .fmp12 or .fm7 or...
A bit simpler than my example generated in the heat of newness...
Hmm, I didn't know one could give one's post a checkmark... In this case, duplicate post, duplicate checkmark... :)
And just to add to the "mea culpas" the developers friend script: Saving Sequential Back Ups During Development that I have shared with many here is another case where "laziness" used an explicit reference to .fp7. Jack's method here would be a good way to update it to work with either file extension...
"RightWords ( Get(FilePath ) ; 1) returns the file extension, .fmp12 or fp7"
When I use that with a file called "My File.fp7" it returns "File.fp7"
"." & RightWords ( Substitute ( Get(FilePath ); "." ; " " ) ; 1 )
Someone must have edited my post... :)
I use this to set the variable $$_extension so I only have to do it once in a startup script that sets 6 utility variables.
Since Filemaker does not provide the extension when using things such as Database Names, I have to append it when using the files in various functions.