Hi Todd: Here's how it works, assuming your solution is closed...
- In Finder/Windows Explorer, rename your database file; for example, "My Notes" is renamed to "Research Notes".
- Navigate to the "Files" folder where all of the externally stored container files are kept.
- Locate the folder named with the old name of your solution ("My Notes" in this example), and rename the folder to the new name ("Research Notes" in this example).
- Open the renamed database file and choose the menu, File > Manage > Containers.
- In the Storage tab of the Manage Containers dialog, double-click the base directory that points to, [database location]/Files/My Notes/.
- Change "My Notes" in the path to "Research Notes", and click OK twice to save your changes.
If the externally stored container field is on the startup layout (so FMP attempts to render it before you've changed the base directory path), it may not display the container contents after you've edited the path. Just close and then re-open your database file to force it to redraw the container using the new base directory path. HTH.
Does this same instruction apply if the file is hosted?
For example if I have a file that was initialled name File1 was using open storage where the base directory was using File1 and I just renamed this file and loaded it to a different server it looks like the new base directories is still pointing to File 1.
How do you go about changing that?
The real problem it seems to me is that 12 won't manage remote storage on remote volumes in a hosted environment so all your documents get pushed to the local volumes of your FM server. I understand why FMI did this but it's a non-starter for lots of my customers unfortuneately.