Search results for query: *

What would happen, and it took a while to find out what was happening, was that the recursive would work for the first few passes then starting passing random data or data from previous passes. I was never able to determine. John

Not surprising. We made the mistake of upgrading from 2008 to 2009. It ran our macros at least 20% slower and recursives no longer worked so I had to rewrite a lot of stuff to get around it. Eventually, I know, we are going to have to upgrade, but we will put it off for as long as possible...

If you hit F8 (F5 is run) it will go line by line. You can also set toggles to stop it. The F8 step by step will show you where it hangs up. John

Good luck! We have run into this before when upgrading from 2008 to 2009. All of a sudden recursives didn't work (it would grab random data and use it to return some rather interesting results) along with some other commands. That issue and the fact that the macros all of a sudden ran 20% to...

Similar issue--- We wanted the work order no and qty on all drawings. The easiest (only) way I could figure out how to do that was to write a "property update" macro which counted all the duplicate parts and assemblies and put the quantity, workorder no, and rev num in the part properties...

This is not a fix but, what I do, is do the "select other" thing. Then you move the mouse around (even if you can't see anything) but eventually something pops up on the select other and you can check if it is what you want. Usually works for me. In fact, I often have to do this even when...

I know - but this is what pops up with Google.

Finally figured this out. The code listed above doesn't work and any combinations tried resulted in interesting (and wrong) results. Some of these results could not be fixed in code. Unless I am missing something, the guys at SolidWorks have some serious bugs or, more likely, didn't bother...

We do most of our design via VBA /Excell/Soliworks programs. We use common drawing files so that means a drawing file has to handle hole sizes that change. Holes can change from various tap sizes to various drilled hole sizes in the same location. I have been doing this by suppressing unused...

We do most of our design via VBA /Excell/Soliworks programs. We use common drawing files so that means a drawing file has to handle hole sizes that change. Holes can change from various tap sizes to various drilled hole sizes in the same location. I have been doing this by suppressing unused...

value = Part.GetCustomInfoValue("mud", "material sz") If value = "" Then matsz(x) = Part.GetCustomInfoValue("", "material sz") This reads value from the custom properties (material sz in this case - this is used for a BOM macro)for the "mud" configuration. If the property does not exist in...

vaL = CwResult.GetReactionForcesAndMoments(1, Nothing, swsForceUnitlbOrlbin, ErrorCode) I am posting this 3 places in hopes somebody knows.This command, as far as I have been able to determine, doesn't work. The help says it returns an array of forces and moments. As near as I can determine...

vaL = CwResult.GetReactionForcesAndMoments(1, Nothing, swsForceUnitlbOrlbin, ErrorCode) I am posting this 3 places in hopes somebody knows. This command, as far as I have been able to determine, doesn't work. The help says it returns an array of forces and moments. As near as I can...

The way I did it (it was for a BOM that sorted the stuff so it printed out in the same order every time - the SD way was driving the inventory and shop guys nuts to try to track changes) was to open the assy and find the children. You then you can read all the children properties by using a get...

Yup, I have the same issues. I have developed a combination of Excell sheets and macros to automatically generate our standard line of stuff. It works pretty well to the point where a significant amount of time is spent cleaning up the drawings. I have looked into auto scaling. It would work...

I have had problems similar to that. Sometimes the equations will not update untill you go into the equation editor. You don't have to do anything, just hit OK. I THINK it happens when some of the equations use the values from other equations, but I haven't spent the time to track that down...

I think I go this... For the tables to be linked, I had to set all the cells equal to the respective cell in the external excel file. The design table will then be reading the external excel file. This way, you can have lots of design tables in different model/assys reading one exernal excel...

Ok, I think I get it. My stuff has fastener files which, for a lot of reasons that appeared good at the time, are labeled 1,2,3... I ran into the same problem, really wanted to know what it was by just looking at the config labels. The think is a $PARTNUMBER. My code activates the...

Ok, I am dense. I think you are missing the following Set prop = partfle.extension.customproperty manager_("configuration name" or "" for the root) long=prop.set("prp name",prp value) or long=prop.add2("prp name",swcustominfotext,prpvalue) John

I think you need to activate the configuration you want to play with. The rather bizzarre command for this (at least the only one I have found) is partfile.showconfiguration configurationname partfile is a modeldoc2, configurationname is a string John