![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
A saving of the bacon... not!
Feb. 20th, 2013 10:31 amOne of the things I don't like about translation memory programs that work outside the file format of the source document (which seems to be most of them) is that if—heaven forbid—something happens to make it impossible to export the finished work back into the required file format, you are likely to have a good opportunity to exercise your "people skills" as you explain to your client exactly why the work is late.
My situation is not that dire, at least not yet.
A little while ago, when I attempted to export an Excel file, memoQ vomited a System.Runtime.InteropServices.COMException at me, and according to what I see on the memoQ group on Yahoo!, this problem seems to crop up periodically.
The most recent cry for help, dated last September, appears to have gone unanswered, which was not encouraging. On the other hand, a ray of hope was offered by a reply posted last July, which noted that "despite the error, the exported file (named as 'exported.xlsx') can be found in..." followed by path information that is largely no longer valid, but which did point me in the right direction, which is to say: I found the file.
And while Excel on my work machine will "open" the file and not complain, the end result is that nothing is displayed.
The reply suggested that the problem may be on the Excel side, although I sort of tend to doubt that, as the only thing that has changed in my setup since the last time I successfuly exported a file from memoQ to Excel was upgrading to the latest version of memoQ. Still, I've got a "repair" going under way for Office as I type this.
While the repair process is running, I'm going to complete this post and then see if the 'exported.xlsx' file is usable in LibreOffice.
UPDATE: I just tried opening the file on the Asus, and there, Excel does report a problem with the file and offers to recover it... recovers it... and the recovered file appears to be okay! (And "repair" is still running!)
WHEW!
Now, I just have to check it over, which seems infinitely preferable to the alternative! (The LibreOffice experiment will have to wait until later.)
Daylight is burning! Deadlines loom ahead!
UPDATE: Repair is complete. Setup informs me a system reboot is required.
Just. Wow.
POST-DEADLINE UPDATE: The repair apparently had some effect. Excel on my work machine now also complains of the same error and offers to recover the file.
My situation is not that dire, at least not yet.
A little while ago, when I attempted to export an Excel file, memoQ vomited a System.Runtime.InteropServices.COMException at me, and according to what I see on the memoQ group on Yahoo!, this problem seems to crop up periodically.
The most recent cry for help, dated last September, appears to have gone unanswered, which was not encouraging. On the other hand, a ray of hope was offered by a reply posted last July, which noted that "despite the error, the exported file (named as 'exported.xlsx') can be found in..." followed by path information that is largely no longer valid, but which did point me in the right direction, which is to say: I found the file.
And while Excel on my work machine will "open" the file and not complain, the end result is that nothing is displayed.
The reply suggested that the problem may be on the Excel side, although I sort of tend to doubt that, as the only thing that has changed in my setup since the last time I successfuly exported a file from memoQ to Excel was upgrading to the latest version of memoQ. Still, I've got a "repair" going under way for Office as I type this.
While the repair process is running, I'm going to complete this post and then see if the 'exported.xlsx' file is usable in LibreOffice.
UPDATE: I just tried opening the file on the Asus, and there, Excel does report a problem with the file and offers to recover it... recovers it... and the recovered file appears to be okay! (And "repair" is still running!)
WHEW!
Now, I just have to check it over, which seems infinitely preferable to the alternative! (The LibreOffice experiment will have to wait until later.)
Daylight is burning! Deadlines loom ahead!
UPDATE: Repair is complete. Setup informs me a system reboot is required.
Just. Wow.
POST-DEADLINE UPDATE: The repair apparently had some effect. Excel on my work machine now also complains of the same error and offers to recover the file.
