Posts
New technology is great, but sometimes presents us with some challenges. 64-bit computing is giving some great gains in performance, but has provided some unique challenges as well. The primary challenge is that 64-bit architecture and the older 32-bit architecture have some interoperability issues (interoperability challenges seem to be the GIS professionals constant companion), and applications on either architecture have some problems communicating. Microsoft has worked around this by providing an emulator to allow 32-bit applications to run on 64-bit systems, which is why we can still run most of our old 32-bit programs. One of the areas that has been later in development has been drivers for Microsoft’s Open Database Connectivity (ODBC). These ODBC drivers allow Windows to serve up, or publish different database for applications to use. The drivers for Microsoft’s Jet database (The engine used by Microsoft Access) were unavailable.
What difference does this make to the GIS user? Well many of the datasets we use rely on ODBC to make the data available to our software. AutoCAD Map 3D used these ODBC drivers to access data through FDO as well as Map data links (link templates). In 32-bit versions of AutoCAD Map 3D, we can drag an Access (Jet) database or Excel file onto the Map Explorer and have it become a Data Source that I can view the data or use it to link to AutoCAD objects. Users who have moved to 64 bit systems (such as myself), could no longer do this. We also couldn’t use the FDO connectors to connect to many of our databases, as they were based on ODBC drivers as well. Microsoft released new drivers, and this made FDO connectors available, but the link templates were still unavailable. That’s because the Link Templates rely on ODBC as well. AutoCAD Map has calls to the Microsoft Jet drivers to make the drag and drop possible. The problem is that Microsoft never released a 64-bit Jet driver (at least in name). Instead they have released the Office Access Connectivity Engine (ACE). The new drivers for ACE were available after the Map release so it wasn’t part of the 2011 release.
The good news is that you can load those drivers and use your Link Templates again. You can’t drag and drop, but you can manually create the links. You’ll have to manually establish the data set through ODBC, and then you can connect to the data in Map 3D. The Autodesk Map 3D support team has a blog with a link to the drivers, instructions, and a video on manually setting up the ODBC connection and connecting in Map.
Keep in mind, Microsoft has set the default install for Office to be 32-bit, so you need to make sure you select the 64-bit version to get the new drivers. When I first installed Office 2010, I accepted the defaults assuming it would load the 64-bit version. As I found out, with the 32-bit version of Office installed, you can’t install the drivers. In that case, you’ll need to uninstall the 32-bit version, and reinstall the 64-bit version of Office (or the drivers). I understand you can load the 64 bit drivers, and then reinstall your 32-bit version of Office (2010 or previous version) – I haven’t tried it since I have made the jump to Office 2010. Let me know how it goes if you try it.
