In-context Relationships

We have been running into many problems with in-context relationships...
I believe that it has been since mid 2001+; We skipped 2003 and are now
running with 2004.

I'd appreciate some feedback regarding our methodology:

We design and manufacture products (sheet metal) that often have several
sizes.

For a complete product that has several sizes, we would create a
configuration for each size at the assy level and component levels.
There would be one component that drives the model and the components
attached to that would have in-context to the assembly releationships
so it would update accordingly.

Our drawings of that component would have several sheets to display the
different configurations.

This methodology used to work up to about mid 2001+, but has broken
since and has continued to stay broken throughout the entirety of 2004.
I haven't tried on 2005 yet, but I will be going through it soon.

What is strange about this situation is that our parts' drawings seem to
work (showing the different configs correctly) until we either open the
assy or part and start activating the different configs. After doing
this, the only drawing views that display correctly is the currently
active (or saved) config.

Now we find this to be very dangerous (and so far costly), as I have
always been under the impression that this was a core
feature/functionality of SolidWorks and basically the main jist of the
marketing for several years (since configs became available).

I have read that many are not using in-context relationships due to
inconsistencies and performance, but I believe that we are not 'doing it
wrong'.... But maybe there is a better way.

We have had a suggestion from our VAR to use assembly sketches to layout
the features we want related, but I would surely think that we wouldn't
need to go to that extent as that is a massive duplication of effort in
my opinion.

Thanks for any light that can be shed on our dilemma


David Short

 

Hey D...
If I am to understand the overall view of whats been happening. YOu
are working in Top down assembly mode. And you are relating multi part
files to just one part file that will drive them all? And that prior
to 2001+ all was working fine. But when you open them up in 2004 the
get all wacky?

I guess what I am trying to see is if this is something that, if you
were to remodel from the ground up in 2004 would you experience the
same problem. (I know that, that is not a viable solution, just trying
to ascertain where the data is getting corrupted) One of the best ways
to narrow down a problem with the software is to be able to reproduce
it.

You might be able to talk with your VAR and see if it is something
that can be sent directly to SW HQ. Let them have a go at it and see.
I know, like most of these guys, that SW does try to be all to all,
and in that they might fall short. They do listen to customers,
probably better than any other CAD package out there. Question is,
what is the justification for something that is still an issue after
2-3 years of it being an known issue.

 

Thanks for everyone's replies... SolidWorks has identified the problem
and has issued a SPR on it and are being very helpful in diagnosing the
problem.

We have tried many methods, including modelling from scratch in 2004,
but the problem is the stability of this functionality.

Bottom line is that the folded up configurations of the components are
displaying correctly, but the flat patterns (derived automatically in
the drawing) are not. So derived configurations which are *not* in
context to the assy in this case is seeming to be the problem.

Hopefully this one won't go by the wayside as some other show
stoppers.... I think this is a very big one and needs to be addressed ASAP.

Our VAR has also suggested to use assy layout sketches to drive multiple
relationships, which works as a work-around, but forces us into a lot of
duplication of effort.