jaeify.blogg.se -

#Solidworks 2010 bump bend part how to#
#Solidworks 2010 bump bend part software#
#Solidworks 2010 bump bend part code#

You should have a good idea of where to go from there. Set swApp = CreateObject("SldWorks.Application") Once you’ve created a new macro, you’ll need to go to Tools–>References and add in “SldWorks 20XX Type Library”.

To create a new macro, start typing a name and then click Create, otherwise select a macro from the list and choose Run, Edit, or Delete.

Click the Macros button on the far right.

To created, edit, run, or delete an Excel macro, follow these steps: They must be stored in the Excel document, and they must be run from there. Macros cannot be saved as external files. You cannot store a SolidWorks macro in a SolidWorks document and then run it from there. In SolidWorks, the VBA macro is its own file (.swp). First, a note about the differences between SolidWorks and Excel macros.

#Solidworks 2010 bump bend part how to#

Now that we know how to run Excel from SolidWorks, let’s do just the opposite. Interesting in learning how to create a 3D point cloud in SolidWorks using point data stored in an Excel spreadsheet? Check out Lesson 7.1 on our Videos page. Two notes: 1) The Win32 API call is used to properly shut down Excel, otherwise a residual EXCEL.EXE process can remain that interferes with future attempts to use Excel, 2) If you get a compile error that says “User-defined type not defined”, it probably means that you did not set the correct references. SwApp.SendMsgToUser2 Cells(row, 1).Text, swMbInformation, swMbOk (Place this sample spreadsheet in C:\ to use the following example.) Make sure that Excel is not already open while you run this code.ĭeclare PtrSafe Function PostMessage Lib "user32" Alias "PostMessageA" (ByVal hwnd As LongPtr, ByVal wMsg As Long, ByVal wParam As LongPtr, ByVal lParam As LongPtr) As Longĭeclare Function PostMessage Lib "user32" Alias "PostMessageA" (ByVal hwnd As Long, ByVal wMsg As Long, ByVal wParam As Long, ByVal lParam As Long) As Long

#Solidworks 2010 bump bend part code#

As an example, here’s some code that will display a message box for each row in the first column of a spreadsheet. Indeed, unlike SolidWorks, there is no “Excel API Help” contained with Excel. Beyond that, learning how to work with the Excel API is really just as simple as using the Object Browser and Google a lot. Notice its similarity to the code we use to get ISldWorks. Now, to connect to Excel we’re going to use this code:

Locate “Microsoft Excel 14.0 Type Library”, click the check box next to it, then click OK on the References dialog box.

In the VB Editor, go to Tools–>References.

Setting up the reference to the Excel library is as simple as this: You could control Excel, Word, and Access in your SolidWorks macro if you wanted.Įnough technical background. Indeed, you can reference as many libraries as you want. Now here’s the big takeaway: if you want to integrate Excel API code into your SolidWorks macro, it is as simple as referencing the Excel libraries alongside your SolidWorks libraries. VBA can’t “see” the API for an application unless its libraries (.tlb. What I just wrote about SolidWorks is true for Excel or any other application. You can see them if you go to Tools–>References while in the VB Editor. Guess what? By default, your SolidWorks VBA macro does references these libraries. If you want your VBA macro to understand SolidWorks API code, your macro must REFERENCE these type libraries. By default these libraries are located in the root directory of your SolidWorks installation. Rather, SolidWorks Corporation chose to expose SolidWorks API interfaces and calls and store them in “type libraries”. Very convenient!īut here’s an important point that many novice API programmers miss: VBA doesn’t automatically understand SolidWorks API code. Consequently, SolidWorks users get to use the same language and development environment to program in both SolidWorks and Microsoft Office.

So that’s what SolidWorks Corporation chose to do-use VBA as one way to create macros in SolidWorks.

#Solidworks 2010 bump bend part software#

They also made VBA available to third-party software developers (like SolidWorks Corporation) to integrate in their software. Why is it so easy to integrate the Excel and SolidWorks APIs using Visual Basic for Applications? Microsoft created VBA as a way for users to program with the APIs of their Office products. As a bonus, I’ll also cover how to include an Excel macro in SolidWorks design table. While I am not going to cover all of the material presented in that lesson, I do want to provide you with a basic run-down of using the Excel API in a SolidWorks macro, and vice versa. Given the ubiquity of Microsoft Excel in engineering departments worldwide, it is no surprise that our “Using Microsoft Excel with the SolidWorks API” tutorial, available to Premium members, is one of our most popular.