SW 08 Glitches

[NL8]

Greetings all,

Recently downloaded the image for the SW 08 0.0 install. SW definitely outdid themselves on this version.

What it seems is that a critical issue in 07 for my company has been fixed in 08. What I'm curious about is what other glitches have people seen with the 0.0 version and how serious they think they are.

Long story short I have to do a sort of cost/benefits analysis on whether the known issues in 08 are worth dealing with if they solve the problem that 07 hasn't.

 

[Razberryjones]

What problem are you specifically refering to? I will have to undertake the same process shortly. SW 07 so severely interupted our normal operations for so long, that my supervisors are afraid to even mention 08.

 

[Theophilus]

I jumped to SP0 of 2007 when confronted with major problematic limits in Animator (and a tight deadline). That proved to be a big mistake. I jumped toward the improved/new features promised by 2007 and had whole (complex) assemblies corrupted as a result--probably something near 100 wasted hours on that project (yeah--18-hour work days to hit the deadline--no fun).

So--look before you leap. Test it out first with something similar (not your "real" files--or at least use copied files) since you cannot revert 2008-touched files to a previous version. If you don't hit any snags, you can probably get away with using SP0 for that particular work.

I like the new features that come out, but simply cannot be put in the position I was in last year waiting desperately for SW corporate to check out my service issues and incorporate fixes into a future SP1. This sort of thing can damage your business (or your health), so be careful. Testing is probably the best thing you can do.



Jeff Mowry

http://www.industrialdesignhaus.com

Reason trumps all. And awe transcends reason.

 

[NL8]

The problem we were having was having parts dragged into subassemblies and randomly changing configurations who dragged from the top level assembly to the sub assembly. We've found work arounds since, considering that SW still hasn't seen fit to incorporate a fix for that into a SP. I'm leery about leaping myself, and have been testing operation on '08 on old files from before we went to PDMWorks. As of this moment it appears to me that 08 0.0 is more stable than 4.0 of 07. I share the woes that you guys suffered with 07 though, even if we waited until 2.2 before we leapt. there was incredible data loss and file corruption and many lost hours and sleepless nights.

Hence my post.

 

[SBaugh]

Sorry to hear about your loss of sleep, but for the most part SW07 and SW08 has been very stable for me and most of our customers. There have been a few files get corrupted, but that cannot be avoided in anyway. SW will crash and if your saving a file or working on a file its very likely it will corrupt the file. It might not be corrupted so bad that it shows the corruption the next time, but its just something that cannot be avoided.

SW08 changed the some of the ways Configs are made and that might be why your having problems or questions in SW08. Have you been through the What's New? If not, I suggest that you look at the portion on Configs.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

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

faq731-376

 

[Florent]

Like Theophilus,
we migrated all ours workstations (about 15) on 2007 SP0.0. And it was a very very bad experience and without come back way ...

Today, I've got a special workstation on which I'll made a lot of tests before expand 08 on our 'work' computers.

But, there is the counterpart : a lot of important SPR logged in SW support are only fixed in 2008 and not in 07 SP5 !!!!

I hope my tests will be quick and concluding ...

SW2007 SP4
Worksatation HP wx4300 2GB
NVidia Quadro FX 3450

 

[rockguy]

Here's a very simple but show stopping glitch for us. If you use "feet & Inches" units for your measurements and you want to display your dimension as 2'-4" and not the default 2'4" the option to do this is currently NOT working in SW 2008 Sp0.0.

Rob Rodriguez CSWP

http://www.axiscadsolutions.com

http://www.robrodriguez.com

http://designsmarter.typepad.com/rob_rodriguez/

Eastern Region SWUGN Representative

http://www.swugn.org

http://www.nvtswug.com

SW 2007 SP 2.0

 

[SBaugh]

Its always best to wait for SP1.0 before moving anyways... That is what we recommend for our users. But that does not mean to not test it in SP0.0, just don't use for production... and even when SP1 is out, still test for a few weeks before implementing.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

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

faq731-376

 

[Heckler]

Testing new releases should be done before any real data is converted. It just makes good sense if you care about your intellectual data.

Heckler
Sr. Mechanical Engineer
SWx 2007 SP 4.0 & Pro/E 2001
o
_`\(,_
(_)/ (_)

This post contains no political overtones or undertones for that matter and in no way represents the poster's political agenda.

 

[NL8]

SW08 changed the some of the ways Configs are made and that might be why your having problems or questions in SW08.

The config problems we've been having have been in '07 not '08, but I've been able to replicate them in 08'. I'm not sure if it's just because the data is still in '07 format or what, but none the less.

a lot of important SPR logged in SW support are only fixed in 2008 and not in 07 SP5 !!!!

They released SP5?!?!

 

[Florent]

They released SP5 !!!

Yes, I've been informed by my VAR for a SP5. I'd a "not official" date : 09/17 ....

Note that for the 08 SP0, they said me the 09/13.

I think we can hope the SP5 before october ... , unless they took delay for 08 version ...


SW2007 SP4
Worksatation HP wx4300 2GB
NVidia Quadro FX 3450

 

[NL8]

It puts a tear to my eye Florent, it really does. Maybe they dealt with my SR.

 

[RawheadRex]

Back when I had a "real job" I used to jump right in with the new releases of SolidWorks because I wanted all of the new bells and whistles. Then we got hosed while working on a major sub-assembly and didn't have benefit of backups to do a regression (dumb-dumb-dumb-dumb-dumb....you get the point). Needless to say I caught some hell for that and learned my lesson.

After I moved on to my next job the guy I worked for there actually had been with SolidWorks doing Product Definition for a few years. He wouldn't ever jump over to any new release until at least service pack 2. I took that to heart and coupled his wisdom with my own experience when I went to work for a VAR. Here's a few items that I've been sharing with customers in anticipation of 2008:

1. Are you sure you want to go with 2008 SP0 straight off?
2. Are you REALLY sure that you want to jump into 2008 SP0?
3. If you're hell-bent on jumping right in then make back-ups of EVERYTHING just in case you have a need to rollback.
4. Do testing on the converted 2008 dataset. Try to break SolidWorks 2008.
5. Are you ABSOLUTELY POSITIVELY certain that you want to run with 2008 SP0?
6. I recommend waiting for the first service pack of any new SolidWorks version

Last year with 2007 SP0 a serious bug with custom properties was uncovered AFTER it came out. SolidWorks issued a Hot Fix but not before this nailed a number of our customers. It's great software but it's certainly not infallible. My belief is that one should take care when making the jump to the next major version.

Cheers,


Chris Gervais
Application Engineer
CSWP, CSWST

 

[NL8]

We have run with that same custom over the years, waiting until at least SP2 before jumping. But it's starting to look like SP0 of 08 could have a major fix in it that SW has been slow to fix in 07. waiting on this fix basically crippled us for the time and SW's "suggested workaround" was scotch-tape over an open wound underwater. we've limped around it, but if '08 can fix it then the pro's might just outweigh the cons.

 

[SBaugh]

If your SR doesn't get a lot of support from others seeing the same problem, it might not get dealt with until many revisions later. The lower the amount of people see the bug the lower on the pole it gets and the slower your issues will get to be fixed.

If you have a workaround that lowers your chances more also.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

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

faq731-376