I have pasted a note from the help section regarding VBA insolidworks and 64 bit applications. ---beginning ofpaste---Microsoft Visual Basic for Applications (VBA) is a 32-bitapplication that Microsoft is not porting to Windows x64.
If you are using SolidWorks x64 and your SolidWorks VBA applicationis a DLL, then VBA will attempt to load the DLL into its processspace and fail (e.g., Active X error when attempting to instantiatean object). The failure occurs because you attempted to mix 32-bitand 64-bit applications.
SolidWorks x64 can communicate with SolidWorks VBA if SolidWorksVBA is a separate 32-bit process. All communication then goesacross process boundaries that Windows x64 can manage. If you movethe object causing the failure to an x64 executable (.exe) insteadof a DLL, then your application will work as expected.---end ofpaste---I have a macro that is inserted into each of my parts.Since this is a large assembly, I might find it a little easier towork with in a 64 bit environment. The problem is
WHEN I AM WORKING IN A 64 BIT ENVIRONMENT THE MACRO DEBUGGER COMESUP EVERYTIME THE MACRO IS ACCESSED. THIS CAUSES THE DEBUGGER TOOPEN AND I MANUALLY HAVE TO CLOSE IT DOWN TO CONTINUE. THIS ISUNWORKABLE IN MY ASSEMBLY. IS IT POSSIBLE TO DEACTIVATE THEAUTOMATIC BUGGING FEATURE.?SolidworksApi macros
If you are using SolidWorks x64 and your SolidWorks VBA applicationis a DLL, then VBA will attempt to load the DLL into its processspace and fail (e.g., Active X error when attempting to instantiatean object). The failure occurs because you attempted to mix 32-bitand 64-bit applications.
SolidWorks x64 can communicate with SolidWorks VBA if SolidWorksVBA is a separate 32-bit process. All communication then goesacross process boundaries that Windows x64 can manage. If you movethe object causing the failure to an x64 executable (.exe) insteadof a DLL, then your application will work as expected.---end ofpaste---I have a macro that is inserted into each of my parts.Since this is a large assembly, I might find it a little easier towork with in a 64 bit environment. The problem is
WHEN I AM WORKING IN A 64 BIT ENVIRONMENT THE MACRO DEBUGGER COMESUP EVERYTIME THE MACRO IS ACCESSED. THIS CAUSES THE DEBUGGER TOOPEN AND I MANUALLY HAVE TO CLOSE IT DOWN TO CONTINUE. THIS ISUNWORKABLE IN MY ASSEMBLY. IS IT POSSIBLE TO DEACTIVATE THEAUTOMATIC BUGGING FEATURE.?SolidworksApi macros
