Hmmm… I haven’t ever done that (moved projects to a different drive) so I’ve never seen that problem, but I can understand why it’s happening.
When you use a dynamic asset in a project it knows that asset by an absolute path, not a relative path. So if that path changes (for example, moving the asset file to a new folder or new hard drive) that path in the database will be wrong.
(On the other hand, if you only moved the project to a different drive and both drives were still hooked up, everything should still work.)
Off the top of my head I can’t think of a great way to handle the problem (in future versions of CPM) - if an asset can’t be found maybe show a list of assets with the same name and allow you to say, “Yes, that’s the one”? Which means you’d have to “repath” an asset once, but after doing that for one project CPM would “know” about those assets and repathing the ones in other projects could be done more quickly.
I’ll move a project to another drive and try to experience what you have to see if that helps me figure it out.
Sorry for the problem and if anyone has an idea for this, don’t hold back.
Jay
[import]uid: 9440 topic_id: 23315 reply_id: 93356[/import]