G
Guest
I apologize if this has been asked before. I've found many references to my
problem but no clear, seemingly logical resolutions.
The problem: My son used WMM to create a school project. As with all
school projects, all files were saved on a usb drive. All was well, no
problems, until he tried to work on the project at home. In moving from a
computer at school to the one at home, the different computer configurations
cause a different drive letter to be assigned to the usb drive. Once this
happens, all his file import links are broken and he gets the dreaded "red X"
problem.
Ok, a pain, but we figure he can just browse on the new drive and reconnect
all his links. However, when doing so, he gets the "The file you selected
doesn’t match the original file closely enough to be used as a replacement."
This happens despite the fact that the file IS the original file.
First, I'm amazed that in this day and age they are still hard coding the
full file path. But ignoring that, is there any easy way to recover here?
One suggestion is to use disk management to reassign the drive letter to the
one that WMM expects for the files. I can do that but it will involve
reassigning drive letters on several of my home computer drives to create
that slot. This solution also requires admin privs, something I'm reluctant
to give my son at home, and something the school absolutely (and
understandably) won't do for the school systems.
I can help him recover this one time through seemingly convoluted steps.
But how do we avoid this problem on future projects?
Moving between computers with a mobile storage device does not seem that
unusual. Is it really the case that WMM can't handle this?!!!!
Thanks.
problem but no clear, seemingly logical resolutions.
The problem: My son used WMM to create a school project. As with all
school projects, all files were saved on a usb drive. All was well, no
problems, until he tried to work on the project at home. In moving from a
computer at school to the one at home, the different computer configurations
cause a different drive letter to be assigned to the usb drive. Once this
happens, all his file import links are broken and he gets the dreaded "red X"
problem.
Ok, a pain, but we figure he can just browse on the new drive and reconnect
all his links. However, when doing so, he gets the "The file you selected
doesn’t match the original file closely enough to be used as a replacement."
This happens despite the fact that the file IS the original file.
First, I'm amazed that in this day and age they are still hard coding the
full file path. But ignoring that, is there any easy way to recover here?
One suggestion is to use disk management to reassign the drive letter to the
one that WMM expects for the files. I can do that but it will involve
reassigning drive letters on several of my home computer drives to create
that slot. This solution also requires admin privs, something I'm reluctant
to give my son at home, and something the school absolutely (and
understandably) won't do for the school systems.
I can help him recover this one time through seemingly convoluted steps.
But how do we avoid this problem on future projects?
Moving between computers with a mobile storage device does not seem that
unusual. Is it really the case that WMM can't handle this?!!!!
Thanks.