Sorry I can't get your problem. The screenshot shows "relative" path at [hosted location], it means no problem, not "old server".
I did try a REPAIR on the file.
I hope you only did that on a *copy* of the file, not on the file you continue to work with.
The 'repair' actions is not meant for maintenance or regular troubleshooting, it has but one purpose: to try and get data out of a damaged file so that you can import that data into a good backup. The repair process may decide to trash schema and/or data elements if it thinks that will let you open the file to get the rest of the data.
Last Post for today.
I have a template solution that I modify for each new client. One of these file started back in FM 9 and was upgraded time after time until the current FM 14.
The problem I am just now noticing is that the file appears to think it is still the original file.
Meaning that you took a copy of the old file and renamed it in the OS? Then what you are seeing is normal because what is in the screenshot is just a hard-code string that got its value the first time that functionality was used. Just change it. Or use the Developer Tools to rename the file, that is much better at finding references to the old file name.
Can you tell me more about Developer Tools?
Here is a way to reset the old file name appearing in PDF's (this was done in FMPA14 on a Mac).
Open FMPA without opening any files.
Go to the "Recover..." menu item in the File menu.
Select the file in question.
Select the "Use Advanced Options" checkbox and click on Specify.
Select the "Copy file blocks as-is" radio button.
Click on the the "Delete cached settings..." checkbox.
Does that resolve the issue for you?
Thanks I will give that a try.
Philip Gershwin | Gershwin Consulting | www.Gershwin-Consulting.com
323.600.5439 | email@example.com
Sadly No. The save to relative still states the previous installation.