'The docfile has become corrupted' error message 1

[Nella95]

What I've always done in the past is save my work - maybe re-boot the computer, then start again. It's never really been a problem for me. Is this the 'right' way to do things? Or is there another method I wasn't aware of?

SW Professional 2012
64 bit SP1.0
Intel Xeon X(R) CPU 1603 0 @ 2.80 GHz
8.0 GB of RAM

 

[CorBlimeyLimey]

What are you working on when you receive that error message?
Does SW crash or freeze or ??
Do you have a sample "corrupt" file?

 

[Updraft]

For good preventive maintenance I try to run the SolidWorks Rx --> System Maintenance every week, plus I shut my computer off every night.

CBL's question is spot-on. We need more details of your problem to give more specific help.

- - -Updraft

 

[Nella95]

CBL- SW does not crash or freeze - As every computer user knows, you have to get into the habit of saving at least after every major part completion - so when I save, after it's done saving it gives me that error message - my personal feeling is the file isn't really corrupt at all.

I think this is a non-problem. Just wanted to be doing it most efficiently.

SW Professional 2012
64 bit SP1.0
Intel Xeon X(R) CPU 1603 0 @ 2.80 GHz
8.0 GB of RAM

 

[SBaugh]

Best way to determine if there is something wrong is send the file to your VAR and ask them to if they would send the file to SW and have them Scrub the file to see if there is any corruption in the file. That is the only way to know for sure... however getting a VAR to do that can be a problem at times... varies between VAR's.

If you setup the Backup and Auto recover properly, then if SW were to crash, then you may not lose as much. Everyone crashes, but what you do to help yourself from making it a pain staking task if you forget to save some where is what separates everyone.

Regards,

Scott Baugh, CSWP
Berry Plastics
Cad Admin\Design Engineer
GEASWUG Greater Evansville Area SWUG Leader

http://www.scottjbaugh.com

"If it's not broke, Don't fix it!"

faq731-376