SOLIDWORKS has updated the Visual Basic for Application environment in 2013 release from VB6 to VB7.VB6 is 32bit application while VB7 is 64bit application.Due to the difference in variables size in 32/64 it is required to use PtrSafe keyword to assert the environment that it is safe to run the macro in x64 systems and LongPtr or LongLong to properly resolve the Long type variable in 32 and 64 bit environments.
I am a new lab view user, i am trying to connect lab view with solidworks to simulate and control in my assembly. after installing labview 2016 64bit, and installed also soft motion module (LabVIEWSoftMotionModule2016f1) and activated it in lab view but i don't see the softmotion appear in lab view window when i am starting new project neither my assembly. this what i see every time. how i can solve this problem.
I have a c# application that runs on both 32-bit and 64-bit OS.In my app, how can I programatically check that solidworks is installed or not on computer.If we can check it by reading registry key ,then provide me path for both 32-bit and 64-bit.Tell me if there are other ways also to check it.
No. Unfortunately, SOLIDWORKS is no longer supported on 32bit computers. The last supported release of SOLIDWORKS on 32bit computers was SOLIDWORKS 2014 which is no longer available for download as an educational version.
I think the general rule is use the 32 bit client by default unless there is a strong reason to use the 64bit version. We have some users using the 64 bit version as we have a customisation that uses some Solidworks dlls that are 64bit only. There was also an issue with Epicor Data Discovery and the 64 bit client. Given most (99%) people use the 32bit client all the bugs have been ironed out. not so with the 64 bit version.
Another this that might be happening is startswinstall.exe spawns other EXEs to do parts of the installation.
Now because SCCM uses the SYSTEM account, it has 2 user profiles when it comes to %TEMP% folders: one for 32bit apps and one for 64bit apps.
$#it hits the fan when you have 32bit self-extracting EXE extracts to C:\WINDOWS\syswow64\config\systemprofile\AppData\Local\Temp then it launches a 64-bit EXE. The 64bit EXE will then look in to C:\WINDOWS\system32\config\systemprofile\AppData\Local\Temp but the files are in the other folder.
Minimum System Requirements