GOOGLE DRIVE ISSUE: ACAD error message - Sorry, we couldn't find G:\.SHORT-TARGETS-BY-ID\....\DATA.XLSX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
First post so be gentle 😉
About a year or so ago google changed something and everyone in the company that uses google drive through windows explorer had to reset all quick links because for some reason the actual file path for any file is now preceded by the ".SHORTCUT-TARGETS-BY-ID\a long random set of characters\".
Since that happened we started getting this message when trying to open a dwg. The workaround seemed easy, you just open the Excel file and then the error clears and you move on. But of course sometimes you will be working on the drawing and it tries to autosave and then the error comes up again, so you go hit save on the Excel file and then you can clear the message and move on.
Then this gets really annoying when you want to open a previous cad file and you can't because the message would force you to close the Excel file you are working on to open the one in the folder of the previous file you are trying to open because these template data sheets use the same name and excel can't have two files of the same name open at the same time. So the workaround on that ended up being to copy the previous cad file I want opened into the folder of the one I am currently working in, since all my data links are relative paths and I never use full path, it will then just look for the excel file I already have open.
Another thing to note is that, until I have opened or saved the Excel file so that ACAD can see it, it will not let me move past this message. I feel like you should be able to acknowledge the message and clear it even if the file really doesn't exist, but that is not the case. you are stuck until you get the referenced file open.
My partner and I are tired of the nuisance of these workarounds and copying files just to open them up. I'm hoping someone can figure out what is going on here. I realize that this was probably created by google but I'm hoping there is a real fix out there so we can take these annoying little bumps out of our workflow.
Thanks
[ The subject line of this post has been edited for clarity by @pendean File Storage Location was Added: GOOGLE DRIVE ISSUE: ]