And how many years, have we all been told to stick with AlphaNumerics in naming conventions?
hint: the answer is...
about 2 decades
Now you know another reason why!
On Jun 14, 2015, at 10:51 AM, Taylor Sharpe <email@example.com> wrote
I ran into an interesting situation that I didn't realize. If you have a filename with a period in it, then FMP13 can't open it if hosted on FMS14. For example a file named "data.something.fmp12". An FMP14 can open it. And an FMP13 can open it on an FMS13 server. It is only when you have FMP13 opening a file hosted by FMS14 that it is a problem. emove the period and replace it with an underscore or space and all is good.
So just be warned to watch out for periods if you want backwards compatibility with your FMS 14 server for earlier version FMPs.
It is a defacto standard supported by the major operating systems.
They make sure that the OS know which application should be used with this file. In this case it is telling FileMaker Server that it should try to open the file, while other files will be ignored.
So everything after the first "." will be interpreted by FileMaker Server as the file type suffix.
But FileMaker Server is a little bit stricter than the standard. The standard is to only interpret the last set of characters after the last period.
One popular method used by many operating systems, including Windows, Mac OS X, CP/M, DOS, VMS, and VM/CMS, is to determine the format of a file based on the end of its name—the letters following the final period.
And Beverly is of course right: Follow the conventions, lower ascii lettes and numbers and maybe underscore in file names. And at many other places in FileMaker as well.
Anybody who is interested should have a look here:
How to see them on Windows
Carten: And Beverly is of course right: Follow the conventions, lower ascii lettes and numbers and maybe underscore in file names. And at many other places in FileMaker as well.
Yes... us developers generally know and stick to the standards. But as usual, the problem file was one uploaded by the client. It even had open by Admin with full access and no password. Soooooooo..... needless to say, standards were not being followed at all - haha. But it was just interesting that FMP 14 had no problem with it and FMP13 only had a problem if it was on FMS 14, but no problem if on FMS 13.
This is why us developers get paid, to clean up things like this. I was actually trying to get the client all upgraded to FM 14, but they still have several old Mac 10.7 and 10.8 machines. Trying to get them to replace those, but for now, they have to stick with FMP13 since FMP 14 won't install on those old machines.
Yes, we should probably do something to promote the conventions at the public forum.
Carsten: Yes, we should probably do something to promote the conventions at the public forum.
Yes, as you and Beverly point out, standards really are important.
I just looked through the Devcon 2015 schedule and no one has a topic with "Standards" in it. Maybe that would be a good topic for Devcon... standards to follow to help make solutions successful. And there are some competing standards, but understanding, picking, and sticking to a standard at least for each solution is a really good idea (don't mix and match standards in a solution). Maybe something for Devcon 2016!