Word 2010 and Endnote x3 compatibility

Has anyone experineced Word 2010 and Endnote x3 compatibility issues?

The EN X3 add-in crashes Word 2010 immediately on opening. Following advice given on the Office 2010 Beta forum, I had to open Word 2010 using the “/safe” switch and disabe the EN add-in. The response from Thompson Reuters to an enquiry was that compatibility will not be provided until X4 is released next year.

They are not sure even with Win 7. Based on my past experience, I would wait trying Endnote for >6 month when new OS or new word processor comes out. I’m pretty much sure I’d see some kind of problems with betas.

Office Suite 2010 works great using either Windows 7 Ultimate or Vista Ultimate. If your work uses EN x3 with Word, then it is highly recommended that you wait until Endnote fixes the compatibility issues with Word 2010. They might come out with a new EN x4 to be in alliance with Word 2010. Since Office Suite 2010 is still in Beta, there might be enough time for Endnote to fix the problem.

I had to uninstall Office Suite 2010 and re-install Office 2007 to continue using Endnote x3.

Firstly, Office 2010 runs well on all versions Vista and Windows 7 not just Ultimate.  Naturally the if you’re running the 32bit versions you’re restricted to the 32bit version of Office 2010; 64 bit versions of Windows Vista and Ultimate will run both albeit not simultaneously.  Secondly, a compatibility update will be possible with the 32 bit version, but much more difficult on the 64 bit version.  Given that it took X3 to finally work with Office 2007 SP2 on a 64 bit system, this may be more challenging and most likely will require significant, but not impossible, changes to function in native 64 bit mode (read: new version).  Some notes from Microsoft directly about Office 2010 which should answer some questions about future compatibility.

Side-by-side installations    No support is provided for side-by-side installations of 64-bit and 32-bit editions of Office, including across applications. For example, there is no support for side-by-side installations of the 2007 Microsoft Office system 32-bit with Office 2010 64-bit, or for Microsoft SharePoint Workspace 2010 64-bit and Microsoft Excel 2010 32-bit.

Deployment Considerations A key consideration is that you cannot install native 64-bit Office 2010 on computers that have 32-bit Office applications and third-party add-ins installed. You must uninstall the 32-bit Office applications and add-ins before you can install 64-bit Office 2010. If you have 32-bit third-party Office applications and add-ins that are required for users, you can install the default option, which is 32-bit Office 2010 (WOW64 installation) on computers that run supported 64-bit editions of Windows.

Advantages of running 64 bit Office

Running Office 2010 64-bit provides the following advantages:

  • Ability to use additional memory.
  • Excel 2010 can load much larger workbooks. Excel 2010 made updates to use 64-bit memory addressing in order to move beyond the 2-GB addressable memory boundary that limits 32-bit applications.
  • Microsoft Project 2010 provides improved capacity, especially when you are dealing with many subprojects to a large project.
  • Enhanced default security protections through Hardware Data Execution Prevention (DEP).

Disadvantages of running 64 bit Office

The following issues might affect compatibility:

  • Microsoft Access MDE/ADE/ACCDE files    Databases that have had their source code removed (such as .mde, .ade, and .accde files) cannot be moved between 32-bit and 64-bit editions of Office 2010. Such databases that are created by using 32-bit Office (any version) can be used only with 32-bit Office, and a database that is created on 64-bit Office can be used only on 64-bit Office.
  • ActiveX controls and COM add-ins    ActiveX controls and add-in (COM) DLLs (dynamic link libraries) that were written for 32-bit Office will not work in a 64-bit process. As a result, Office 2010 64-bit solutions that try to load 32-bit ActiveX controls or DLLs will not work.

In addition to controls that load into Office applications, there are also Web-based solutions that use ActiveX controls in Microsoft Internet Explorer. Office 2010 64-bit editions install Office 32-bit client-side controls for supporting Web solutions in a browser.

The workaround for resolving these issues is to obtain 64-bit compatible controls and add-ins or to install Office 2010 32-bit (WOW).

  • Office Graphics (OArt)   For Excel integration, conversion of OLE, form controls, and ActiveX to CompatE2os in Excel 2010, some controls are not available in 64-bit Office 2010. An example is the Microsoft Date and Time Picker Control 6.0 (SP4), which is accessed on the Excel 2010 Developer tab, by clicking Insert , and selecting More Controls under ActiveX Controls section.

Graphics rendering    There are differences between the 32-bit and 64-bit Graphics Device Interface (GDI) that might have performance implications because of the lack of MMX support on 64-bit. Intel’s MMX technology is an extension of the Intel architecture (IA) instruction set. The technology uses a single-instruction, multiple-data (SIMD) technique to speed up multimedia and communications software by processing data elements in parallel.

  • Visual Basic for Applications (VBA)   VBA code that uses the Declare statement to access the Windows application programming interface (API) or other DLL entry points will see differences between 32-bit and 64-bit versions. The Declare statement must be updated with the PtrSafe attribute after inputs and outputs to the API have been reviewed and updated. Declare statements will not work in 64-bit VBA without the PtrSafe attribute. New data types are added to 64-bit Office 2010 VBA: LongLong and LongPtr. For more information about VBA, see the “64-bit VBA Overview” and “Declare Statement” articles in the Microsoft Visual Basic for Applications online Help in Office applications.

General feature deprecations

The following feature deprecations may affect compatibility:

  • Microsoft Access    The Replication Conflict Viewer is removed from both the 32-bit and 64-bit installations of Office 2010. This functionality can still be implemented by using the ReplicationConflictFunction Property. ReplicationConflictFunction is a Microsoft Visual Basic for Applications (VBA) routine in the running database that can be used to resolve synchronization conflicts.

  • Publisher    The Microsoft Works database converter (wdbimp.dll) is removed from both 32-bit and 64-bit installations of Office 2010. This converter was previously used in the Mail Merge functionality to connect to a data source created in Microsoft Works.

  • Word    Microsoft Office Document Imaging (MODI) and all its components are deprecated for both 32-bit and 64-bit Office 2010. The legacy Equation Editor is not supported on 64-bit Office 2010, but is supported for 32-bit Office 2010 installations (WOW64).

  • WLL (Word Add-in libraries)   WLL files are deprecated for both 32-bit and 64-bit Office 2010. A WLL is an add-in for Microsoft Word that you can build with any compiler that supports building DLLs.

Setup Process for Office 64 bit

  1. Setup checks for 64-bit Office 2010 prerequisites.

When you run Setup.exe from the x64 folder, Setup determines whether 32-bit Office applications are installed. If Setup detects 32-bit Office applications, it displays an error message that informs users that they must first uninstall all 32-bit Office applications if they want to continue with the installation of Office 2010 64-bit. The error message lists the installed 32-bit Office applications. If Setup does not detect 32-bit Office applications, it installs the 64-bit edition of Office 2010.

![](http://i.technet.microsoft.com/Ee681792.note%28en-us,office.14%29.gif) **Note:** When you run Setup.exe from the x86 folder, Setup determines whether there are 64-bit Office 2010 applications installed. If Setup detects 64-bit Office 2010, an error message is displayed and Setup is blocked. If Setup does not detect 64-bit Office 2010, it installs the 32-bit edition of Office 2010.

Office Professional Plus 2010 and Microsoft Office Professional 2010 will also be available as a combination release (DVD media) that includes both the 32-bit and 64-bit editions of Office 2010. If Setup is run from the root folder of the Office 2010 DVD that contains both 32-bit and 64-bit Office 2010, Setup performs the installation as follows:

  • On a computer that runs a supported 32-bit edition of Windows, Setup installs the 32-bit edition of Office 2010.

  • On a computer that runs a supported 64-bit edition of Windows, Setup checks for installed 64-bit Office applications, and then continues as follows:

    • If no 64-bit Office applications are installed on the computer, Setup installs Office 2010 32-bit. Office 2010 32-bit is the default installation on a 64-bit Windows operating system (uses WOW). This also applies if the administrator upgrades an existing 32-bit Office installation.
    • If 64-bit Office applications are installed, Setup installs Office 2010 64-bit.
  1. Setup reads XML data.
  2. Setup builds the feature tree.
  3. Setup creates the local installation source.
  4. Setup installs Office 2010.
  5. Setup applies the 64-bit OCT customization .msp file.
  6. Setup applies software updates.

Message Edited by SkullTrail on 11-27-2009 03:30 PM

Kao nima de. Nengbuneng jiejue wenti? luoliluosuo de shuole zhemeduo,bu xianlei?

Thanks. But You havt kicked off the problem.

There is no solution to the compatibility issue with Word 2010 and Endnote x3 or x2. We just have to wait for Endnote to fix the problem. Word 2010 works awesome without Endnote addin. However, I tried using Reference Manager 11 and surprisingly it works with Word 2010. Although I do not have Referece Manager 12, I would expect it to work with Word 2010 as well.