Solidworks added a great feature in 2013 by allowing parts to be replaced with "parts with the same name but different file location." At my company we like to keep purchase part models in a folder near the project folder we are working on for various reasons. Sometimes I reuse assemblies from previous projects which have common purchase part models. Typically I save the purchase parts "as a copy" and place them in a folder near my new project (keeping in mind that I don't have any other models open at the time).

Now that I can replace parts in 2013 with ease I decided to run a test and saved the entire assembly "as a copy," renamed it, and placed it in my new project folder. I fully expected to have to open the assembly in the new project folder and replace all the purchase parts so that they would map to my new project purchase parts directory. Solidworks already assumed I would need the parts in the new directory and replaced them for me. Maybe this is something SW has always been able to do, I'm not sure. The search algorithm must be looking at near-by folders first as it looks for parts. I'm not sure if we should be worried or if there is a way for Solidworks to prompt before it replaces parts.