Software quality and stability issues should be reported to your VAR

[josephv]

Hello,

I noticed that there are several issues in this forum dealing with software quality and stability issues.

In my opinion these issues must be reported to your VAR or SolidWorks. Although, there are many excellent tips in this forum, only the programmers can improve the quality of the software.

As for stability issues, there are many causes for poor stability (installing with antivirus turned on, video card, Network problems), but these issues must also be reported to your VAR or SolidWorks, after all they are the ones that have more familiarity with all the causes.

Cheers,

Joseph

 

[JNR]

Actually, folks, you should NOT do your COMPLAINING through enhancement requests. All you will get is a form email telling you that bug and deficiency reports should go through your VAR. I speak from experience.

So..... If you have a genuine enhancement request, use the SolidWorks ER process. If you have a complaint, go to your VAR. If your VAR will not listen then go to your SolidWorks regional manager. (...and next time the VAR will listen - looks like magic, smells like magic, but it's just the good old carrot and stick routine!!)

BTW: Fixing these issues is dealt with by two separate groups in SolidWorks. Those who fix today's problems and those who are working on the next revision. (You might be surprised where some of the actual bug fix coding is done!) Also remember that you have to be reasonable about what constitutes an enhancement. Making the software work with brand X graphics board is NOT an enhancement. This is not unique to SolidWorks, it is a generally applied policy in the industry.

 

[MadMango]

Thanks for the clarification.

Ray Reynolds
Senior Designer
Read: faq731-376
"Probable impossibilities are to be preferred to improbable possibilities."

 

[StarrRider]

josephv

This is not a solution, but if you have a web site you can speed up the process a lot. Dump the files into a directory your web can see and call your var. Let them know what the problem is as you see it and then give them the URL and possibly a password.

You might also ask us to look at the problem. Remove anything proprietary first and throw up a questionnaire sheet asking for specifics like – Real name – Company – SW version & SP – Operating system - Comments - and what ever else you can think of that might help. When you think that enough people have responded, send the information to your VAR AND the Regional Manager. You would be building a case for fixing the problem that overwhelms any considerations about the size of your company. – Stating that “47 other users tested this assembly and here is what they have to say.” Might have a little more weight than 2 or 3 people have this problem.

Lee

If all else fails, there is one simple solution - run FDISK and start over.

 

[JNR]

Actually, Lee, I think it is an excellent solution. Another variation on the carrot and stick routine. If none of us can fix it, it's probably a genuine problem AND there's now a lot of unhappy customers, plus publicity.

 

[StarrRider]

JNR

They may be few and far between, but at times – I do have come up with a good ideas.

Lee

You must remember one thing. You are UNIQUE!!! Just like everyone else!!!