pdybeck,
I think yes you are doubling your work. With no bill of mat'l on the face of the drawing, you are referencing a reference in your erp (item 79).
You already have the data for the part number loaded into your erp somehow, so you could just use that.
I have also seen a practice here...
Here are a few things I've tried:
1. Set suppression state with "configure component" tool.
2. Set suppression state with Edit menu, unsupress with dependants...all configs.
perplexing...
I am working on an assembly and drawing. I have saved the files and checked them in and have noticed that each time I open the files, the suppression state of one particular Toolbox part (Pan Cross head_ai)reverts to unresolved in every instance.
I need ideas! what could be happening?
Is there...
ANOTHER STAR FOR RGRAY...
Removing the double toolbox problem fixed it. I tested this today and low and behold, no more "panheadcross is already opened. Do you want to view..."
AND:
as a bonus, the toolbox works properly now...no more jumping to extents and ending the screw drop function...
Alex,
You are so right. re-booted, started a new session of SW and started a new assembly. Plopped the same piece of hdwr in that I was having trouble with and !viola! It works properly that way. What would be the culprit if you had to guess? The double install?
thanks again,
Jim
¿)...
thanks for the replies. I will check on the items that you listed. I have seen another location on root, but didn't think it would matter since there is no db there. And sw is not pointing to it. I got a systems admin that is really good, so he can help me sort this out the rest of the way...
Does anyone else ever get this kind of behavior from ToolBox?
I grab a 8-32phms from the TB and it reports "pan head Cross_ai is already opened. Do you want to show the open file"?
I select yes, then drop the toolbox part on its default ref mate and check the green check confirming the...
sytem options, external references, dont prompt to save read only...
¿)
Version of SolidWorks: 2009
SolidWorks Sercive Pack:sp3
Operating System & Service Pack: winxp pro v5.1 (sp2)
Graphics Card and Driver version: Nvidia Quadro fx540, 9.1.3.6
Amount of installed RAM: 3GB
Virtual Memory...
right click in the vault view and select "display labels as" and then check descriptions.
dsgnr1
¿)
Version of SolidWorks: 2009
SolidWorks Sercive Pack:sp3
Operating System & Service Pack: winxp pro v5.1 (sp2)
Graphics Card and Driver version: Nvidia Quadro fx540, 9.1.3.6
Amount of installed...
make sure that "select all references" is checked under pdm options, command defaults before you open the assem.
dsgnr1
¿)
Version of SolidWorks: 2009
SolidWorks Sercive Pack:sp3
Operating System & Service Pack: winxp pro v5.1 (sp2)
Graphics Card and Driver version: Nvidia Quadro fx540...
Mitsu50,
Having the same problem. Intermittant problem using the pdm module with Solidworks. I haven't found a good answer to this or an equal work around. Just wanted to make you aware that someone else has seen this.
dsgnr1
oh! Then, depending on your Nema spec., I think we used a phone type jack and phone chord in a device. The chord passed along the outside though.
Good idea of utilizing the mech swivel as a trough though.
dsgnr1
the search button works pretty well. I typed in "external thread" and found this thread thread559-198008. It has a bit of information.
dsgnr1
¿)
Version of SolidWorks: 2007
SolidWorks Sercive Pack:sp5
Operating System & Service Pack: winxp pro v5.1 (sp2)
Graphics Card and Driver version...
Gat,
sorry for the intrusion but wanted to advise of a work around that we discovered this morning.
thread559-210690
I think I referenced one of your old threads.
dsgnr1
¿)
Version of SolidWorks: 2006
SolidWorks Sercive Pack:sp4.1
Operating System & Service Pack: win2k v5 (sp4)
Graphics Card...
We were seeing a similar issue with configured bom as in thread559-184576. Intermittent bom numbering scheme problems with item numbers starting at 2 or 3 or 4. This is a very isolated problem it seems as there is little information on several fora.
The workaround:
In table properties...
I would agree to a slow down, but think that updating (or catching bug fixes) as an option would wreak havok on the file translation aspect. My scenario goes like this: A vendor and I have the same release, however, he has a couple fixes in his that allow some feature that my machine can't...