this is a confirmation for me (old Windows freak), that the old convention not to use dots in a filename is right.
If not "right", then precautious.
At the moment, mac runs on an Unix system, the precaution turned to be an obligation (I would say).
It remembers me on something ...
When a dot was used in a filename, but within 4 places far from the extention dot, some function didn't work, but if it's more than 4 places, then it worked.
Nicolaus and I wrote about it.
Maybe the bug is still existing for all those cases ...
Try it :-D
With this_is_my_file.12345.fp7, the function will work.
With this_is_my_file.1234.fp7, the function will not work.
First problem: Fabrice Ricker (April 2006) FileMaker-Version: 8.02 ... FieldType ( FileName ; FieldName )
Second problem: Nicolaus Busch (December 2006) FileMaker 8.5 ... FieldNames ( FileName ; LayoutName )
Next week in Zürich, I presume?
About dots in file names: personal I could avoid it. But some clients have their own filing system. And debugging this bug is a time-waster: how could I know that a different file name is the cause of a 'damaged' database, meaning, functions are not behaving than they used to do.
You work longer with FileMaker than I do. That gives you an advantage detecting bugs. And I am not even talking about printing problems. ;-)
And yes, Zürich it is!
Thank you for your post.
This problem has been previously reported, and the suggestion from Testing is that "test.v1.fp7" is a file "test" with the extension .v1.fp7.
However, the additional information from "fabricker" shows something that contradicts this, so I have sent both posts to our Development and Software Quality Assurance (Testing) departments for further comment. I will keep you posted.
all good, yes AVOID dots in filenames altogether. Now agree with TSGal (tested in 12) - doesn't work with any .dot before .fp12 etc. So for versioning some other mechanism desired. Was puzzled by this for a little while! ;)