![computer for solidworks 2012 computer for solidworks 2012](http://www.cs.sit.kmutt.ac.th/blog/wp-content/uploads/2015/03/11075681_796290600463469_1656791275_o.jpg)
#Computer for solidworks 2012 64 Bit
If, for some reason, you cannot obtain a 64 bit version of this DLL then your only options are 1) find another 64 bit compatible DLL containing a function that does the same thing, 2) write your own DLL with the desired function and compile it for 64 bit, 3) if the DLL works on Microsoft’s COM framework (as opposed to. With the advent of 64 bit architecture, SolidWorks Corporation recompiled this DLL to work on 64 bit computers. An example is the SolidWorks Document Manager (SwDocumentMgr.dll). If someone else wrote the DLL, you will need to search online or contact them to determine if a 64 bit version available. This will allow the DLL to run on 32 or 64 bit systems. If you wrote the DLL yourself, then re-compile the DLL to work on “Any CPU”. Fixing the Problemįixing the problem comprises three steps: 1) obtaining a 64 bit version of the DLL that is causing problems, 2) re-declaring its functions using new VBA7 keywords, 3) including conditional code that allows for backward compatibility on VBA6. Later, if you’re so inclined, you can keep reading and learn the technical “why” behind the dilemma.
#Computer for solidworks 2012 how to
So if you are using any of the Microsoft Common Controls in your user form (e.g., slider, calendar, web browser) then you are using ActiveX controls that will fail in VBA7.įirst I’m going to give you the quick-and-dirty steps on how to (hopefully) fix your dilemma. ocx but are actually still DLLs underneath. This includes ActiveX controls, which have the extension. The reason your macros are failing is because they are not set up to reference 64 bit DLL files, or the DLL files you are trying to reference are not 64 bit compatible. Why is this? Were we not told that VBA7 is 100% compatible with VBA6? The issue isn’t with VBA.
![computer for solidworks 2012 computer for solidworks 2012](https://images.tokopedia.net/img/cache/500-square/VqbcmM/2020/12/15/024bf822-1eb2-4c35-8ea6-bd5e6d9aeec6.jpg)
When you try to run the macro, you may get the following error. That being said, you may have discovered that some of your macros no longer work in SolidWorks 2013. Nothing about the SolidWorks API itself has changed that requires modification. For this reason, all SolidWorks API code that you write in pre-2013 should work in 2013, and vice versa. VBA7 is 100% compatible with VBA6 (the version included in SolidWorks 2012 and earlier). This is great news for several reasons, the most significant being: 1) VBA user forms no longer pop-up behind the SolidWorks application window, and 2) it proves to us that both Microsoft and SolidWorks Corporation are serious about maintaining the VBA language, which is the language of most SolidWorks API code.
![computer for solidworks 2012 computer for solidworks 2012](http://www.cic.iitkgp.ac.in/image/solidworks/solid15a.png)
SolidWorks 2013 includes VBA 7-the latest version of Microsoft’s Visual Basic for Applications. If your scenario isn’t covered in the video, then I probably cover it in this article.