This has been an issue with AutoCAD for several years. Although Autodesk makes sure that both 32-bit and 64-bit versions of their software is available, some third-party add-ons will only work with the 32-bit versions.
If you have a 64-bit OS and have some of these expensive addons, then you really want to install AutoCAD as a 32-bit program. See here for a method that should allow you to install AutoCAD 2008 as 32-bit on your 64-bit computer if that's what you really need to do.
The fact that the OP would have two Program Files folders leads me to believe his computer is 64-bit. I have the same scenario on my 64-bit (home) computer which has 32-bit versions of 2004 and 2007 as well as 64-bit versions of 2010 and 2011.
We have a new workstation that runs 64-bit, and the installation is defaulting to the 64-bit version instead of giving an option on whether to install 32-bit or 64-bit. I can't find any options for this, or any information on this elsewhere.
#1: The *32 in task manager denotes a 32-bit process running under the WOW64 subsystem (Windows on Windows 64-bit). When you install on to a 64-bit OS you should get short cuts for the 64-bit version, but by the looks you are running the 32-bit version.
Now I'm trying to migrate to AutoCAD 2013 (64-bit) on Win 7 (64-bit), the Ms Access being 2010 (32-bit). From my study of forums and other websites / autocad help etc., I gather that all my problems are due to vba 6 being 32-bit and asynchronous process with AutoCAD 2013 (64-bit) process. I guess I've following options (all considering Windows 7 64-bit only):
ii) Use AutoCAD 2013 32-bit........I think this is not possible as OS is 64-bit. Even if it's possible, then the VBA will still be asynchronous and may cause handshake / interface problems with autocad.
iii) Upgrade to AutoCAD 2014 64-bit with VBA 7 64-bit.........This seems good, but then I face problems in connection with 32-bit MS Access ! Looks like I will have to up[grade Ms Access to 64-bit aswell OR use ODBC 64-bit to connect to 32-bit MS Access. Either way, the DB connection is very toublesome.
This way, you can use all latest version of AutoCAD (2013/14/15) with in-process 32-bit VBA. All your existing code should work without the problems derived from 64-bit AutoCAD and 32-bit out-process VBA.
If the data access to *.mdb/*.accdb is via ADO, you need to install MS Access Database Engine 64-bit. If the CAD computer does not have MS office installed, this is not an issue. If the CAD computer needs to have 32-bit MS Office, it must be MS Office 2010 or 2013 (including MS Access or not), and the 64-bit DB engine's install is a bit tricky. If the 32-bit MS Office installed is Office 2007, then the 64-bit DB Engine cannot be installed. So, the data access is likely not a big issue here.
If the VBA apps have rich UIs, you might have bigger issue: there is almost no 64-bit controls comparable to 32-bit version available. Even as simple as Open/Save File Dialog, you need to write complicated Win32 API code, which most VBA coders have no idea how to do it.
Before you decide to use AutoCAD 2014/15' 64-bit VBA, you'd better just try to load your existing DVB files into acad2014's 64 bit VBA IDE and do a compiling to sfind out how many 32-bit components that break the VBA projects in 64-bit environment. and have to be replaced. Then you need to find and identify 64-bit equivalents (very rare) and workaround (meaning changing code and workflow logic). Again, deepending oour existing VBA projects, it often turns out that moving into VBA 64-bit is not much easier than moving to .NET API, or going back to LISP.
64-bit computing has arrived to the PC market. If you are working with large CAD files (over 20 MB) or performing complex modeling operations you are likely to benefit from speed improvements gained by the access to more RAM which a 64-bit architecture allows. This is a benefit you can begin to realize even with 32-bit programs running in 64-bit Windows. Full 64-bit computing (processor, operating system, and program) will allow access to huge amounts or RAM and eliminate the architecture-based memory ceiling problem with very large files.
The next release of KeyCreator will be available in two versions, 32-bit and 64-bit. The 32-bit version will be the right version for most users since they are still running a 32-bit version of Windows. The 64-bit version can only be used in 64-bit Windows. If you are running 64-bit Windows and have over 3-4 GB of RAM, you should consider installing the 64-bit version. Over the next several months Kubotek will be conducting 32-bit vs. 64-bit performance testing on a workstation with 12 GB RAM. These results will be published around the time of the release and make the advantages of the 64-bit version clear.
One of the key points here is that the 2011 family is the first one where 64-bit is supported.
CMS IntelliCAD 8.3, and following, is available in 64-bit (x64) only because x64 is about 30% faster than 32-bit. 64-bit systems are increasingly replacing 32-bit systems. The 64-bit version of IntelliCAD runs faster than 32-bit, but can use all available system memory to handle large drawing files. 32-bit applications can access up to 3GB of RAM on 32-bit operating systems and up to 4GB of RAM on 64-bit operating systems. To avoid such limitation, the CMS IntelliCAD is only available for 64-bit systems starting from 8.2 version.
Declare statements with the PtrSafe keyword is the recommended syntax. Declare statements that include PtrSafe work correctly in the VBA version 7 development environment on both 32-bit and 64-bit platforms only after all data types in the Declare statement (parameters and return values) that need to store 64-bit quantities are updated to use LongLong for 64-bit integrals or LongPtr for pointers and handles. To ensure backwards compatibility with VBA version 6 and earlier, use the following construct:
The UV30 WebBox incorporates the Sun UltraSPARC RISC 64-bit processor with the 64-bit Solaris 8 operating system. The product is fully compatible with other network computing devices, including 32-bit, Intel-based PCs and servers running Linux or Windows NT operating systems.
582128177f