Vba-Macro

The scenario: a supplier sends fifty SolidWorks parts. The files land in the PDM vault. The PDM admin manually fills in the data cards — material, description, part number, revision. Everything is correct in the vault database. But the files themselves have no custom properties. Any downstream tool that reads properties directly from the file (a drawing, an ERP integration, a batch export macro) sees blanks. The natural fix — run the built-in Task Scheduler “Add/Update Custom Properties” task — breaks the data cards. The task adds the file properties and then syncs them back to the data card. Because the file properties were blank when the task ran, the sync writes blank back over the values the admin entered. ...

A SOLIDWORKS user on the 3DEXPERIENCE forum recently posted a batch macro that failed to compile with “Invalid Character.” The macro tried to parameterize a Task Scheduler run with syntax like $$$FOLDER_PATH$$$ and made API calls to CustomPropertyData. Josh Brady identified it immediately: “That is AI-generated code. CustomPropertyData is a hallucinated call. It does not exist in the SolidWorks API.” This failure pattern is now common enough to deserve a direct explanation. SOLIDWORKS Task Scheduler has no built-in parameter syntax. VBA macros cannot receive command-line arguments. There are no token substitutions in macro source code. Here is what works instead. ...

A SOLIDWORKS forum question asked this week: how do you model a curved sheet metal part, and do stamping structures require forming tools? The answer depends entirely on what “curved” means, because SOLIDWORKS handles three fundamentally different curved-sheet-metal scenarios with three different tools — and forming tools are a separate concern from the geometry of the base body. This post maps the decision tree. The Three Curved Sheet Metal Scenarios SOLIDWORKS sheet metal works by tracking a flat-pattern state for every feature. Every bend is stored with a radius, K-factor, and bend allowance so the flat pattern can be computed by unfolding. Curved geometry complicates this in three distinct ways: ...

Most SolidWorks engineers reach for VBA when they need to automate something. It’s right there in the Tools menu, no build toolchain required, and the macro recorder gives you a starting point for anything the GUI can do. Batch exporting drawings from the PDM vault is exactly this kind of task — repetitive, time-consuming, and automatable. What’s less obvious is where VBA’s limits are, and how to get PDM state awareness without switching to a C# application. ...

Every SOLIDWORKS weldment tutorial starts with “Insert Structural Member” and assumes the profile library is already populated. It never explains where those profiles actually live, what format they use, or what to do when the profile you need isn’t there. If you’re trying to automate weldment creation via a VBA macro, the API reference assumes you already have the profile path, which means you need to know the folder structure before you can write a single line of code. ...

“SolidWorks automation” covers four distinct things that are often treated as interchangeable. They aren’t. A VBA macro that exports DXF files is automation. So is a Task Scheduler job that runs every night. So is a PDM Dispatch script that triggers on a workflow transition. So is a C# COM add-in with a custom Property Manager Page. Each approach has a specific setup cost, maintenance burden, and capability ceiling. Picking the wrong one for a given workflow creates either an over-engineered solution or one that fails the moment requirements change. This guide maps the decision. ...

There’s a recurring post format in the SolidWorks community that breaks CAD automation into levels: macros, parametric design, API integration, configurators. The comments are always the same — experienced engineers arguing about which level their team is actually at, and why Level 3 is the sweet spot that most teams never reach. They’re right. And understanding why most teams plateau matters if you’re trying to decide where to invest automation effort. ...