Maybe you guys need to add a few more "if" statements here and there.
Here's another gem.
This one popped up the other day. I couldn't save, save as, pack and go... had to lose my changes in start over. Restarting Solidworks "fixed" the problem.
I've seen that one plenty of times, myself. Cannot remember what I did to solve it, but it's certainly a strange "error".
Can you please submit such cases to your support representative for investigation? My guess is that the value is not exactly 90, but has some non-zero number at some decimal place and the problem is we should be showing the value out to enough decimal places to represent the problem. You could try to verify this by using Tools, Measure with the decimal places set to 8. If it is in fact showing all zeros out to 8 decimals, then the problem should still be submitted for investigation.
Other awesome error message threads:
2 Billion? try 2 billion billion: https://forum.solidworks.com/message/72429#72429
I guess the limits are exclusive.
34717 wrote: I guess the limits are exclusive.
Here's an annoying one I just got again recently. If you have your assembly option set to "No External References", and you try to open an assembly that already has external references, you get this message. It is a warning, not an error, but another example of dialog with OK as the only possible option. How about a button that would cancel loading of the assembly and let you go change that setting first? With a large assembly, it can be frustrating waiting for it to completely load up, all the while knowing you will have to change the setting and close and reopen it.
You can get this one on 2010 SP2.1 Simulation Premium for the low, low price of $15k including subscription.
I've got this error a few times when I change the revision in 'read from file'. I'm not really doing anything with domes here, do I?
There are a few of us from the SolidWorks User Experience group monitoring the thread and for these error messages, we are in fact going and correcting them when they are straight forward typos, spelling mistakes, etc.
The unfortunate thing is that the majority of these are not of that nature. Most of these messages are not intentional but are likely happening when something unexpected occurs (high memory condition, corrupt file, problem with the operating system, etc.) and an unintentional error message occurs. Sometimes, these messages are not even defined by SolidWorks but come from the operating system. Other times, for some reason, the wrong value or portion of text is passed into the message like in the case of a huge number being shown or it saying that a design table is created in Excel 2003 and can't be opened in Excel 2003. Other times, the entire text string for the message (and title bar) may be incorrect; in speaking with developers, this most likely would occur when multiple add-ins are loaded and something is in conflict between the add-ins and one add-in gets text strings from another add-in or from regular SolidWorks.
Since the condition under which these types of error messages occur is unexpected, we can't actually fix it unless we can reproduce it. So, the best we can do is correct the simple typo and spelling mistakes, continue monitoring the forum and look for trends in certain types of messages and do some internal analysis to figure out what may cause them and try to correct them, and ask that if users can reproduce strange errors repeatedly, report them to their reseller so we can get them to our development staff to be corrected.
Damn Dwight, that was too obvious...
I just got this one.
check out this error
Message was edited by: Jacob Cordingley
add Video to view on web
I let Solidworks know and they told me it fixed in 2009 SP05
I now have 2010 2.1 and it still bad
Retrieving data ...