richard cox Posted January 30, 2006 Share Posted January 30, 2006 We have recently upgraded to VW12 and have noticed that sometimes files that have been workgroup referenced become replaced with non VW files such as PDF's or excel documents. These workgroup references cannot be edited as a message comes up saying they are non VW files and if you remove them and re-attach the reference then any viewports or saved sheets that have been set up need to be set up again. Whilst so far this has only happened on small projects that only have a few files referenced to one another and can be resolved relatively quickly our office also deals with some very large projects where if all the references were to drop out it could potentially cripple the project. Has anyone else experienced this or can tech support offer any solution? There have been a few issues like this that have been cropping up with VW12 and it is making me wonder whether we upgraded too soon. Quote Link to comment
quigley Posted January 30, 2006 Share Posted January 30, 2006 Richard, are you mac or pc. If mac, do the referenced files have suffixes atatched, eg, .pdf, .xls, .mcd? Another thing to try is to open the referenced files first and convert them to 12 files. I've never heard of this happening yet. Quote Link to comment
islandmon Posted January 30, 2006 Share Posted January 30, 2006 WGR = FilePath ... if the path gets corrupted so does the WGR. here's a typical path to VW App: "file://localhost/Applications/VectorWorks%2011.5.1/VectorWorks" here's WGR Path to embedded directory: "file://localhost/Volumes/G5-35/%20JBK5108_FOLDER/WGR_Working_FOLDER/WGR_File_v11" The OS is tasked with keeping track of the Directory database . If that database gets corrupted you are screwed. Therefore, a corrupted WGR Filepath may indicate a systemic problem requiring Disk Utilities to re-compile the volume directories. Quote Link to comment
richard cox Posted January 31, 2006 Author Share Posted January 31, 2006 Thanks for your help We sent the corrupted files to our software supplier who had a look at them and was finding some strange things within the corrupted VW file (such as what looked like a preference file for a printer). He also commented that perhaps it could be some kind of diectory problem on our server. This is conceivable as we run Mac workstations and have recently bought a new Windows 2003 server. If we needed to recompile the volume directories as you suggested I'm assuming this is something that would need to be done on the server rather than the workstations. Any ideas about what could have caused this or how we could avoid this happening again in the future? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.