Has anyone had issues with file references which included the ".fp7" in the original file:name?
We simplified all of our Network paths and removed the ".fp7" from file references a few months back as part of a general file cleanup so had no such issues.
I just wondered if the file extensions made any difference, or were rewritten during conversion, or are ignored completely.
Just spotchecking my 11 and 12 versions, I found one instance where we had .fp7 in the file reference and it was resolved in the rewrite.
I converted a 20 file solution. All files ended in the .fp7 suffix. After the conversion I still have the original file set and a new file set with .fmp12 suffix.
The initial development was done using local files so all references were to the files and not an fmnet address so all TO resolved correctly.
BTimm, I would think that when you first open the new 12 solution if there are files it can't find, it will ask for them and let you select the local file. I believe that this will resolve the fmnet links. After that you can move the whole file set to the server and have it work correctly...
Did you find that any Data References which had included the ".fp7" extension in the filepath needed to be repointed?
Yes, Stephen, that's not a problem. But much better to avoid the whole fmnet issue in first place if you can keep the same host name.
I have 28 instances, also not a problem to fix them one at a time or proactively, but any one-at-a-time fix has its limits. :-)
We do intend to keep our existing 11 Server as the FM12 location when upgrading. The problems of file reference changes were enough hassle last time we had to switch to a new server machine, so we will simply accept a short down time to perform the upgrade on the same server.