We currently have a network install of Creo 2.0 with Flexible Modeling Extension available. One department is using some vendors that employ solidworks. That department has been asking how we can open these solidworks files in Creo. In discussions with PTC I've gone through several suggestions on how this can be accomplished.
What did you end up doing for this? We are receiving native solidworks files from some suppliers and want to directly open them. I'm in a particularly odd scenario, though, where I have the option for opening solidworks parts and assemblies on both my primary and test PC (both Win 7 64 bit, running Creo Parametric 2 M090 - the Solidworks file types show up in the Creo Parametricfile open dialog). I have not installed Solidworks Explorer on either PC, and per the PTC support site, it wouldn't work anyway because I'm running 64 bit Creo and as you mentioned, Solidworks Explorer is only available for download as 32 bit - and that combo won't work (per PTC). As CAD Admin, I have a lot of different software on my PCs so I suspect something I've added at some point is making this work.
I've used a clean laptop (Win7 64 bit) and installed Creo 2 M090, and everything I could think of that I have on both my PCs that might have put some hook in the system that is allowing me to directly open Solidworks parts and assemblies. FEA applications, viewers, other CAD apps that can open solidworks files etc, even Solidworks Explorerand Edrawings (grasping at straws)- no change, that install of Creo doesn't have Solidworks files in the file type dropdown of the file open dialog.
About 95% of the computers in our college will be using Windows 8 after the summer. I have just noticed that Solidworks 2013 32bit is not supported on Windows 8 32bit but will install on Windows 7 32bit. Has anyone got it installed to Windows 8 32bit through GP?
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.
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.
Historically, ArtiosCAD provided an export integration with Solidworks 2010 if that solidworks version was already installed on a user system by a previous version of ArtiosCAD. That version was a 32-bit module and will not run in an ArtiosCAD 64-bit version. The ability to create such an output will be removed.
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