Search results for query: *

Hmm...two additional follow-ons: 1. Your suggestion to disable the standard in Toolbox configure browser made the standard disabled in Hole Wizard as well. So far as I understand it, there's no way to enable this standard exclusively for Hole Wizard, n'est-ce pas? 2. Is there some way to make...

Thanks for the help! I've edited as you suggest. Follow-on question: If I want to share these modifications with buddies on my network, is there a file I can copy over one of their files or...even better, store this file on the server and we all point our SolidWorks clients at it?

DesignSmith wrote that Toolbox standards can be edited to adjust hole wizard standards. We use roll taps here rather than cutting taps and this makes the tapdrill different. Can one change the default tapdrill for hole wizard?

SBaugh wrote: > Check out the SW Website Model Library & 3D Content Central 3D Content Central looks to have all the content of SW's Model Library but not vice versa. Is this true? These have everything except the fasteners so I'm looking forward to EdDanzer's offer of help.

I've read through thread559-93913 which discusses updating SolidWorks and running the Conversion Wizard to update part, assembly, and drawing files. Is there a best practice to update files which are checked into PDM/Works? If one has to check out and check back in manually, this could get...

Is there a best practice to update files which are checked into PDM/Works? If one has to check out and check back in manually, this could get painful. Even if there's an automatic method in the conversion wizard, this will get messy. Bumping revision numbers may confuse BOM's for active products.

I most like EdDanzer's suggestion to make a library of fasteners based on as few parts as possible so fasteners can be substituted without losing mates. I'm just getting started with Toolbox and I'm setting up the environment for myself and two other engineers and making this library seems like...

> I am even uncertain as to whether or not one is even able > to make a SW Assy document a child of anything other than > another SW Assy in PDMWorks. That is not to say it isn't > possible rather I have never attempted to do so in the > past. I think I can by checking in the non-SW document...

McMaster-Carr (mcmaster.com) e.g. part number 91829A537 Then pick "show catalog page" to see plenty of other examples

/Program Files/SolidWorks/lang/english/calloutformat.txt is the "HoleWizard Callout Format Definition File". I'm using Toolbox to configure a screw (not a hole). I don't think Toolbox uses this configuration file. Note: I don't want to make all screws UNF...just some of the time.

I'm inserting a shoulder bolt and the default is UNC. I'd like UNF. Is there a way to change this?

I didn't mean a SolidWorks BOM filetype...I'm using an MSWord document...or any arbitrary file type...that you want to make a "parent" in the reference tree to a preexisting branch or node. So far as I can tell, PDM/Works only supports making a new document the "child" of a preexisting node

Has anyone tried this?

I have a SW assembly already in the PDM/Works vault. I want to add a new BOM document (MS Word) which will be the "master document". As such, the SW assembly should refer to it. I can't figure out how to make an assembly already in the vault refer to a new file without deleting it from the vault...

Can one access a PDM/Works vault while offsite (through a firewall, VPN, etc)?

Can the admin configure PDM/Works to allow certain users/groups to see only released versions of parts/assemblies? That means that if I am the engineer and am working on the latest rev, "B06", other people on the shop floor can only access rev "B" (the last released version). Is this possible...

Figured it out with help from our VAR: Solution is to set lifecycle "Released" to allow changes to BOTH primary and secondary rev schemes...because in order to change from rev A04 to B, both schemes are changing. When bumping to a new release (after being in Development), dialog box will...

When I check them in, I "retain ownership"...so yes, I'm still the owner.

What project and sub-project naming strategries have people found to work with PDM/Works? I like the idea of a date code followed by descriptive text: 040326 donut glazer indicates the project was created 26Mar2004 and is for a donut glazer. Do others prefer an assembly number for...