Windows OS has something about 255 chars for max length of full path, so shorter names would be safer.
Some testing has established:
1. This is a limit on filename length. It has nothing directly to do with the path length - a filename (exclusive extension) simply can't have more than 50 characters. Period.
The behavoiur is the same, by the way, whether the file is local or remote, ie on a server or not.
2. FileMaker 14 behaves exactly the same.
Now, if someone can telll me the reason for this limitation, I'll be satisfied. But it better be good ;-))
FM Inc. has acknowledged that there is a 50 character limited with the externally stored container
feature. Here is what they stated -
"This behavior is actually by design. The maximum file name length for a file held in open storage by an
externally stored container field is 50 characters. This was done to deal with an issue where long file
names could cause instability and crashing in FileMaker Server.
This only affects the file name as shown in that open storage folder; as you see, the file name shows
correctly in the container field itself, and if you use the Export Field Contents command to save the
contents of that container field out to another location, it exports with the full file name, so the file
name is not permanently truncated. FileMaker does hold a reference to the full file name and can put it back
I'm pretty adversely affected by this truncation/50 character limit, so would love to know, FileMaker, if it can be removed.