I used to have this problem on my project. I tried quite a few things and am not exactly sure how we solved it. If it happened to me again, this is the first thing I would do. Ask all the users to open the 'Manage Links' menu and have them send you a screen shot. Verify that the paths and files are all the same, if not, make them all the same.
I also played around with the 'hardware acceleration' checkbox in the Options menu. I do not think that solved the problem, but can't say for sure.
Thank you for posting how you resolved the issue.
What I meant by "way" is to make sure that the path everyone uses to access the central file and the linked file must be the same.
There are two ways to find network locations, mapped which uses letters for drives (which it sounds like you are doing) and UNC path. When someone accessed it differently, the path gets saved to the central file, and anyone accessing it differently won't find it.
As you have seen, mapped drives need to have the same letter as well.
The Central file location can be verified and modified if needed under Collaborate > Synchronize and Modify Settings > Central File Location.
Linked file paths are in Manage Links.
Another possibility which happened in the office I work in -
One individuals mapping to our server was different. When John opened the central file and created a local file, the way his laptop was mapped couldn't find the links. John would disregard the links, when John sync'd to central, central file recieved his changes. Meanwhile Jerry is working in his local file from the central file sync'd and recieved John's changes, in which those links couldn't be found. Jerry then was surprised that the model links disappeared. Jerry reloaded links and sync'd to central and to get the model links to reappear. Circular problem when mapping to sever is not consistent among all pc's and/or laptops.
J. Kim Candelario
Access a broad range of knowledge to help get the most out of your products and services.