bemasamoje
New member
I've had two instances where SW's has crashed and corrupted files such that they have to be sent to SW's HQ to be repaired.
In my case I had some 10 files that were unusable (meaning I at a minimun lost the time it took to send them in to get repaired) and could have potentially lost many days of work.
Even the SW's backup files were tainted. Files that weren't even open at the time but had some association (i.e. in the assembly that contained the file being worked on when it crashed) were corrupted with the error.
Good new is that most of the file could be quickly repaired (though our IT people have a deathgrip on our network so I have to get a hold of them to get them from the SW FTP site)
Curious if anyone else has heard or had this error?
We can then talk about what kind of HW/SW config we're using...
JBR
In my case I had some 10 files that were unusable (meaning I at a minimun lost the time it took to send them in to get repaired) and could have potentially lost many days of work.
Even the SW's backup files were tainted. Files that weren't even open at the time but had some association (i.e. in the assembly that contained the file being worked on when it crashed) were corrupted with the error.
Good new is that most of the file could be quickly repaired (though our IT people have a deathgrip on our network so I have to get a hold of them to get them from the SW FTP site)
Curious if anyone else has heard or had this error?
We can then talk about what kind of HW/SW config we're using...
JBR