If you copy your folder, then your original image copies are still in place in the original folder. Thus, the absolute file paths you report will continue to link back to the images in the original folder. That explains why copying "works" and moving doesn't.
OK, fair point re: copying vs moving.
So, back to my original question: do FM consider this behaviour to be correct or incorrect?
I consider it incorrect because:
a) all of the import dialogue boxes imply that the link is relative (ie. you only specify '/subdirectory' rather than the full directory path)
b) insert picture doesn't work like this
c) FM6 didn't work like this
d) this is a royal pain when moving files around, and there doesn't seem to be any easy/elegant way of working around the problem.
Thank you for your post, and I apologize for the late reply.
This is the correct behavior for FileMaker Pro 7 and above. It is a change from FileMaker Pro 6. Please read Knowledge Base Article #549:
This article provides information to transfer your Container field information from one machine to another.
Please let me know if you continue to have difficulty, or if you need clarification.
Thanks for that.
Just wondering still, though:
- why 'Insert Picture' still works as it used to (ie. it only uses the relative file path)?
- why the import option says it is using the relative file path even though it isn't?
Create a calculation field, resulting in text, with the formula equal to the calculation field. You will then see the path of where the file is located. It will give the relative path (image:) as well as the absolute path (imagemac: or imagewin:). The import can use the relative path (file:) and/or the absolute path (filemac: or filewin:).