| Author | Message | ||
     Jeff_hayden Username: Jeff_hayden Registered: 09-2006 Posted From: 216.62.125.199 |
Joe, You're smarter than me so I'm sure you have already thought of anything I could suggest. But here goes anyway. Any chance that the VWF in your first post could be referencing an AutoCAD 2007 or 2008 drawing? In your second post, it sounds like the drawing may be linked to itself. We frequently get users who are moving too fast with their mouse and end up clicking paste-link instead of paste. I hope you get it resolved. | ||
| Joe_calvin Username: Joe_calvin Registered: 09-2006 Posted From: 8.7.87.222 |
Okay, I didn't have to wait too long for the corresponding save error. The following two message boxes are displayed in sequence immediately after the save command.  Yes, despite the title on the second box, this error occurs on File/Save, not File/Open. The user who experiences this error says that it occurs about once a week, while the error on File/Open (previous post) occurs a dozen times a week. Unlike the File/Open error, this File/Save error does actually prevent the user from saving the file. The only work around we've found is to use Save-As. I failed to mention this in the previous post, but this is Cadvance V12. Again, thank you in advance to anyone who can help. | ||
| Joe_calvin Username: Joe_calvin Registered: 09-2006 Posted From: 8.7.87.222 |
A couple of our users have been experiencing an error lately when opening a files. The two messages boxes below open up in sequence.  This error is very inconsistent. It may happen several times a day, or not at all. Three of us have experienced it (one only once) and the rest of us have not. Sometimes both boxes appear, and sometimes only the first. Usually after dismissing the second box, the file will open fine, but sometimes the file will open without reference files. This occurs on random drawings, not the same drawing over and over again. Rarely, this will precipitate problems in saving; I'll try to get a picture of this next time it occurs. The oddest part of the problem is that it did not occur more than 3-weeks ago. Also worth noting, we've seen the problem given two different file servers in two different cities. If anyone has any suggestions or insight, I would appreciate it. Thanks. |